how to display azure storage table data in a workbook

Ruben Verschueren 55 Reputation points
2025-06-10T12:42:04.9666667+00:00

I have some data stored in an azure storage table and would like to display it as a grid in a workbook.

The next step is then to add links so I can select a row and call an endpoint to (re)process the selected data.

how do I query the Azure storage table in my workbook?

Google's AI assistant suggests it is/was a data source you could select when adding a query. So it's either wrong or could be a permissions issue perhaps.

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,645 questions
{count} votes

Accepted answer
  1. Vinay B 500 Reputation points Microsoft External Staff Moderator
    2025-06-13T13:56:17.7666667+00:00

    Hello Ruben Verschueren

    You've correctly identified CORS as the central issue affecting your Azure Workbooks' ability to call a custom endpoint.

    Even if the origin is allowed, failure to set correct Access-Control-Allow-Headers, Access-Control-Allow-Methods, and Access-Control-Allow-Credentials will cause silent failures in Workbooks.

    Function App: Use the following CORS settings in your Azure Function App:

    • Allowed Origins: https://portal.azure.com (avoid wildcard subdomain if credentials are used)
    • Credentials Enabled done
    • Allowed Headers: Content-Type, Authorization, x-ms-client-request-id, x-ms-user-agent
    • Allowed Methods: GET, POST, etc. depending on your scenario

    Refer:

    https://learn.microsoft.com/en-us/azure/azure-functions/functions-how-to-use-azure-function-app-settings?tabs=azure-portal%2Cto-premium#cors

    You've already noted this, but to emphasize: Azure Function Apps and APIM must use an exact match for the Azure portal origin — https://portal.azure.com. Using https://*.portal.azure.com will be rejected if Access-Control-Allow-Credentials is true, per the CORS specification.

    Refer:

    https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS#credentialed_requests_and_wildcards

    If you’re using multiple APIs behind your APIM instance, define the CORS policy at the All APIs scope to avoid missing origins on individual APIs.

    
    <inbound>
    
      <base />
    
      <cors allow-credentials="true">
    
        <allowed-origins>
    
          <origin>https://portal.azure.com</origin>
    
        </allowed-origins>
    
        <allowed-methods>
    
          <method>GET</method>
    
          <method>POST</method>
    
        </allowed-methods>
    
        <allowed-headers>
    
          <header>*</header>
    
        </allowed-headers>
    
      </cors>
    
    </inbound>
    
    

    Refer:

    https://learn.microsoft.com/en-us/azure/api-management/api-management-policies#access-restriction-policies


    Let us know if further assistance is needed. Thank you for your understanding and for taking proactive steps to learn responsibly on Azure.

    We remind you to close the discussion thread by clicking on "Accept the answer" if the information provided was helpful, as this could also benefit other community members.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.