Azure Monitor Baseline Alerts
Download AlertsGlossaryGitHubGitHub IssuesToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeBack to homepage

Known Issues

VM Log Alert policies fail to remediate

Error includes

failed to resolve table or column expression named

Cause

The underlying data is not present in the Log Analytics table.

Resolution

For VM Alerts please enable VM Insights.

Failed to deploy because of role assignemnt issue

Deployment of AMBA fails when there are orphaned role assignements.

Error includes

“error”: {
 “code”: “RoleAssignmentUpdateNotPermitted”,
 “message”: “Tenant ID, application ID, principal ID, and scope are not allowed to be updated.”
 }

Cause

When a role or a role assignement is removed, some orphaned object can still appear, preventing a successful deployment.

Resolution

  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. Select Access control (IAM)
  4. Under the Contributor role, select all records named Identity not found entry and click Remove

Failed to deploy to a different location

Error includes

Error: Code=InvalidDeploymentLocation; Message=Invalid deployment location ‘westeurope’. The deployment ‘ALZARM’ already exists in location ‘uksouth’.

Cause

A deployment has been performed using one region, for example “uksouth”, and when you try to deploy again to the same scope but to a different region you will receive an error. This happens even when a cleanup has been performed (see Cleaning up a Deployment for more details). This is because deployment entries still exists from the previous operation, so a region conflict is detected blocking you to run another deployment using a different region.

Resolution

Situation 1: You are trying to deploy to a different region in addition to a previous deployment. Deploying to the same scope in a different region is not necessary. The definitions and assignments are scoped to a management group and are not region specific. No action is required.

Situation 2: You cleaned up a previous implementation and want to deploy again to a different region. 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 deployment instances related to AMBA and click Delete.

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

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

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.

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