rich-room-61748
04/07/2026, 11:14 PMazure.resources.Deployment with the ARM template URL (same as Portal).
However, during testing I identified an important issue regarding version handling:
• Each preview version (e.g. 7.5 → 7.6) gets a new artifact ID
• This artifact ID is part of the ARM template URL
• If the URL is not updated, deployment uses the previous version
In our case, after publishing 7.6, the automation still deployed 7.5 because it was pointing to the old artifact ID. So currently, the automation depends on manually updating the template URI after each preview publish. 😕
I wanted to clarify:
1. Is there a supported way to dynamically resolve the latest artifact/template for a preview offer?
2. Or is manually updating the artifact ID expected in this workflow?
3. Is ARM template deployment the recommended approach, or should we instead use some other approach for this?
I’ve attached screenshot of Partner Center for context.
Would appreciate your guidance on the intended approach here.modern-spring-15520
04/08/2026, 3:18 PMrich-room-61748
04/08/2026, 9:24 PM