This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 47%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EES%3C/text%3E%3C/svg%3E)
For one of my projects, I'm aggregating information in the browser and have to push metrics to Azure Table Storage. For this, I use the @azure/data-tables dependency and a SAS token.
On the Azure Storage Account, I enabled the CORS settings to allow any endpoint described in the @azure/data-tables dependency documentation.
The API calls to the https://<account>.table.core.windows.net/Tables endpoint work fine. I am able to create my new table or verify if it exists.
When I try to create, update, upsert, ... a record. That is where it goes wrong. Then I receive CORS errors.
I'm guessing there is something wrong or the CORS settings are not propagated to the table API endpoints. Is there a way to get this fixed?
PS: Nothing is wrong with the API call itself, as I tested it out via Postman and the records are created successfully.
Hello Elio Struyf,
Welcome to Microsoft Q&A, thanks for posting your query.
I understand that you have configured the CORS settings on Azure table service however you are encountering CORS errors during the processes of creating and inserting. This issue persists despite the fact that same API calls to the https://<account>.table.core.windows.net/Tables endpoint and are functioning correctly using POSTMAN tool, and you were successfully able to create a new table.
Please be informed that if it's working successfully from other tools/applications and it's not working with a specific application then it might be the issue from the source app.
Therefore, if the API is working fine with via Postman or the records the issue might be with the API endpoints like table operations because Certain operations on Azure Storage Tables might require additional HTTP headers that are not included by default in your CORS configuration. Ensure to test your application after updating the CORS configuration in a non-production environment before deploying to production.
References:
Please let us know if you have any further queries. I’m happy to assist you further.
As mentioned, CORS is configured and working fine for the https://<account>.table.core.windows.net/Tables endpoint. As I used a wildcard for allowed origins, allowed and exposed headers, there is no further configuration required.
This is also what they call the debugging configuration on the dependency:
https://www.npmjs.com/package/@azure/data-tables#create-a-new-entity-and-add-it-to-a-table
I have tried to perform similar calls straight from the fetch client in the browser, and the same CORS issue happen. As mentioned before, it seems the CORS settings aren't propagated to the table APIs to perform these CRUD actions. For example: https://myaccount.table.core.windows.net/mytable(PartitionKey='myPartitionKey', RowKey='myRowKey')
Removed as I thought the answer was not added
The issue was related to the browser extension host that was not able to call the API. For some reason, it only works on the Table API. Moved the API calls to the background service worker and added the extension ID to the CORS-allowed origins. That made it work.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@Elio Struyf I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.
Issue: CORS issue on the Azure Table Storage APIs when calling table endpoints
Solution: Customer shared - "The issue was related to the browser extension host that was not able to call the API. For some reason, it only works on the Table API. Moved the API calls to the background service worker and added the extension ID to the CORS-allowed origins. That made it work."
If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.