Azure Sub account discovery is failing on : Azure - Sub Account (LP) - Orchestrator due to subscription limit per batch - Known Error

Azure Sub account discovery is failing on : Azure - Sub Account (LP) - Orchestrator due to subscription limit per batch Description The 'Azure - Sub Account (LP)' pattern fails to create when a customer has more than 100 Azure Service Account subscriptions and the master account is included in the first batch of results. This causes the LP patterns creation flow to be skipped entirely.

When a customer's first batch of 100 subscriptions includes the master account, Step 8 skips it, and no Service Account is created. Because the subscription count exceeds 100, pagination creates a second page. However, this second page returns no data (the master account was already on page 1 and was skipped). When Step 9 executes without a valid Service Account, the pattern terminates gracefully but the overall LP patterns creation flow is abandoned.

Steps to Reproduce

Execute Discovery on the Azure with >=100 subscriptions

Workaround 1. Go to sa_pattern, open the pattern 'Azure - Sub Accounts(LP)' -

2. Edit the pattern Step 2 - 'Fetch subscriptions'

Go to the 'Body' section , scroll to the end and update the string : \"options\": {\"$top\": 100}}" to \"options\": {\"$top\": 300}}" - essentially - it increases the limit on fetching subscriptions from 100 to 300 or a higher number safe limit, increase it to the desired value.

3. Click Save and then Publish

4. Rerun discovery after the pattern changes are published.