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(169.60000000000002, 48%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
I wanted to add a custom table to the developer portal, so I created a custom widget using react. I have an existing react application, how should I integrate that application with azure custom widget scaffold code?
There is an SAS error when deploy
azure-api-management-widget-table\node_modules\@azure\api-management-custom-widgets-tools\dist\index.js:260
throw new Error("Could not get storage SAS URL");
^
Error: Could not get storage SAS URL
![](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(284.8, 48%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
I am experiencing the same issue. We have no idea how to solve this. Any solution?
![](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(48, 61%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDK%3C/text%3E%3C/svg%3E)
Hello @Abhinandhan K and @Jef Seys , The APIM team recently released a fix for this issue, please update your npm packages. Also here is the GitHub commit: https://github.com/Azure/azure-sdk-for-js/commit/57ce7f065ac8272e010fc0fb77e37d77b81b7e62. The change made was that you can now specify your tenant ID in the custom widget deployment. If you search for 'configAdditional' in the commit, you will see how the tenant ID is being set. You can find the dev docs here: https://learn.microsoft.com/en-us/javascript/api/@azure/api-management-custom-widgets-scaffolder/options?view=azure-node-preview#@azure-api-management-custom-widgets-scaffolder-options-configadvancedtenantid
Edit: There is also a new project on GitHub called the React Component Toolkit that makes it easy to create custom widgets for Azure APIM dev portal. You can find that repo here: https://github.com/microsoft/react-component-toolkit and an entire tutorial write up on Medium here: https://danielkon.medium.com/create-custom-widgets-for-the-azure-api-management-developer-portal-9255bcdba521
![](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(140.8, 35%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Getting exactly the same issue when deploying a custom widget to our developer dashboard.
Did try to deploy the bingmaps widget to our developer dashboard from : https://github.com/microsoft/react-component-toolkit, filled the APIM_RESOURCEID and APIM_OPENURL variables in the .env file and still getting exactly the same message.
Anyone got any clue what the issue here is?
Martin, did you set the tenantId? It should fix the issue deploying the custom widget! I need to add that to my blog post for clarity.
![](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, 43%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDA%3C/text%3E%3C/svg%3E)
@Abhinandhan K Were you able to resolve this issue. Having the same problem on our end too.