Skip to content

Commit

Permalink
Merge pull request #77 from Brunoga-MS/main
Browse files Browse the repository at this point in the history
New known issue during deployment
  • Loading branch information
arjenhuitema authored Nov 20, 2023
2 parents 92f3240 + e3395bf commit 00b8445
Showing 1 changed file with 30 additions and 0 deletions.
30 changes: 30 additions & 0 deletions docs/content/patterns/alz/Known-Issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,33 @@ To recognize the deployment names belonging to AMBA, select those whose names st
If you deployed AMBA just one time, you have 14 deployment instances

{{< /hint >}}

## Failed to deploy because of the limit of 800 deployments per management group has been reached

### Error includes

*Error: Code=MultipleErrorsOccurred; Message=Multiple error occurred: Conflict,Conflict,Conflict,Conflict,Conflict,Conflict.*

### Cause

The limit of 800 deployment for the given management group scope has been reached. More information can be found at [Management group limits](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#management-group-limits)

### Resolution
To resolve this issue, follow the steps below:

1. Navigate to ***Management Groups***
2. Select the management group (corresponding to the value entered for the *enterpriseScaleCompanyPrefix* during the deployment) were AMBA deployment was targeted to
3. Click ***Deployment***
4. Select all the deployments that could be deleted (example: instances of previous depoloyment related to AMBA) and click ***Delete***.

{{< hint type=Note >}}
To recognize the deployment names belonging to AMBA, select those whose names start with:

1. amba-
2. pid-
3. alzArm
4. ambaPreparingToLaunch

If you deployed AMBA just one time, you have 14 deployment instances

{{< /hint >}}

0 comments on commit 00b8445

Please sign in to comment.