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(224.00000000000003, 62%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDC%3C/text%3E%3C/svg%3E)
Until recently we have been creating and testing private offers in the Azure marketplace. As of yesterday, all 7 of our offers are now showing the message "Invalid argument: uiDefinition" after clicking "Create" on the listing page.
In addition, I can see in the browser console log that there is a 403 authentication error, when requesting the artifacts from: https://catalogartifact.azureedge.net/privateartifacts/.../Artifacts/createUiDefinition.json This happens in both Chrome and Firefox. A colleague of mine is also experiencing the same problem so I believe I can rule out a change in my subscription.
Is there a problem in the authentication flow happening in the azureedge server?
![](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(144, 35%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
We have been experiencing similar issues, escalated to ISV customer success team and they are working with Microsoft Partner Center support to troubleshoot. So far most of our Azure Application (Solution Template) offers, which uses CreateUiDefinition.json and MainTemplate.json have been affected.
It looks like MSFT has resolved the issue or reverted the changes implemented. I can confirm my Solution Template is functional again.
![](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(278.4, 74%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBV%3C/text%3E%3C/svg%3E)
Also OK on our side.
On September 15, a platform change was implemented. This change was part of a broader infrastructure update and, unfortunately, unintentionally caused failures in deployment scenarios that relied on delegated SAS tokens, including the one you experienced.
Once the issue was identified, the engineering team promptly rolled back the change. Since the rollback, we have monitored the system using internal diagnostics and have not observed any further failures of this type.
And also fixed on our side too. Excellent!
![](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(44.800000000000004, 1%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAI%3C/text%3E%3C/svg%3E)
We get the same error for a few days. Is there any documentation provided by Azure to address this problem? It seems like many users are experiencing the same thing.
You can report in Azure and open a Support ticket. We already have a ticket that is under review by Microsoft, number (Azure marketplace private pl... - TrackingID#2509170050001590)