feat: Subscription Vending - NRP issue

[ReneHezser]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/ptn/lz/sub-vending

(Optional) Module Version

No response

Description

Sometimes the deployment will fail with "code": "SubscriptionNotRegistered", "message": "Subscription xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is not registered with NRP.".

Since the deployment script also uses networking to create a VNet (at least in my cases), should we wait or retry after the subscription has been created?

This happened in a customer environment, as well as in the GitHub action of the module.

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!