The current model for using the Analyze Layout service endpoint requires polling to retrieve the completed analysis result.

This model is inefficient and resource intensive on the application side. Consider a case when using Azure Functions: this would require multiple Function invocations to check if the analysis is completed.

This can be partially alleviated by incorporating a Shared Access Signature type functionality so that clients can directly query the Get Analyze Layout Result endpoint OR provide a parameter which allows the caller to specify an endpoint where the resultant JSON can be stored as a file.

For example, add two header values to the Analyze Layout request that point to other Azure resources:

Operation-Result-Target: {URL}
Operation-Target-Auth: {Authorization Info for URL}

An alternate is to manage the configuration on the service side (Form Recognizer) and provide configuration of keys and container URIs for Storage Blobs or Queues. Then use a single parameter like:

Operation-Result-Forward: {Configured Forwarding Target}

This would allow for more fluid data flows as it would allow forwarding the result to Azure Queues or Azure Service Bus, for example, which could then trigger a Function or Logic App.