Azure Update Manager | Maintenance configuration

Question

Azure Update Manager | Maintenance configuration

Andrea Longhitano 200

Hello Everyone,

we have created some maintenance configuration in Azure Update Manager.

Even if the name of the resource is tagetik-prod-patching

maintenanceresources
| where type == "microsoft.maintenance/configurationassignments"

User's image

the id of the resource contains an UUID which is wrong.

This behaviour is randomic because for other maintenance configuration the id is correct.

Could you explain why?

Thanks,

Andrea

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-20T12:30:20.5366667+00:00

Hello Andrea Longhitano

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-21T12:06:07.73+00:00

Hello @Andrea Longhitano

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,
Suchitra.

Answer accepted by question author

Suchitra Suregaunkar 16,780 Microsoft External Staff Moderator

Hello @Andrea Longhitano

The GUID in the resource ID is expected behavior, it is not a bug or a random issue.

The query you're running:

maintenanceresources
| where type == "microsoft.maintenance/configurationassignments"

is querying configuration assignment resources, not the maintenance configuration itself. These are two different resource types in Azure:

Resource Type	What It Represents
`Microsoft.Maintenance/maintenanceConfigurations`	The actual maintenance configuration you created (e.g., `tagetik-prod-patching`)
--------	--------
`Microsoft.Maintenance/maintenanceConfigurations`	The actual maintenance configuration you created (e.g., `tagetik-prod-patching`)
`Microsoft.Maintenance/configurationAssignments`	The link/assignment between a maintenance configuration and a target resource (VM, scope, etc.)

As documented in the ARM template reference for configurationAssignments, the name property of a configuration assignment is simply a string, it does not have to match the maintenance configuration name.

User's image

When assignments are created (especially via the Azure portal, dynamic scopes, or Policy), Azure often auto-generates a unique GUID-based name for the assignment to avoid naming collisions. This is why you see a UUID in the id field for some assignments.

The reason it appears "random" where some assignments have a clean name and others have a GUID , depends on how the assignment was created:

Portal or dynamic scope → Azure typically generates a GUID name automatically.
CLI / ARM / Bicep with an explicit name → The name you specify is used as-is.

So, your maintenance configuration tagetik-prod-patching is correctly named. The GUID you see belongs to the assignment object that links it to a VM or scope.

If you want to retrieve the actual maintenance configuration name from the assignment, you can extract it from the maintenanceConfigurationId property in the assignment:

maintenanceresources
| where type == "microsoft.maintenance/configurationassignments"
| extend maintenanceConfigName = tostring(split(properties.maintenanceConfigurationId, "/")[-1])
| project name, maintenanceConfigName, id, properties

This will show you the friendly configuration name alongside the assignment ID.

Reference:

Hope this clarifies the behavior! If you have any further questions, feel free to ask.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,

Suchitra.

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-26T04:21:08.2066667+00:00

Hello @Andrea Longhitano

Thank you for the upvote.

We are glad that the provided information helped you. Along with that Accepting the answer is equally important because it confirms the resolution and helps others in the community quickly find verified solutions. It also reflects the success of our joint effort to resolve your query. If anything is still unclear or you need further assistance, please let us know.

We are happy to help.

So, kindly consider marking the answer as Accepted and this helps other community members who may encounter a similar issue in the future.

Thanks,

Suchitra.

1 additional answer

Your answer

Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-20T12:30:20.5366667+00:00

Hello Andrea Longhitano

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-21T12:06:07.73+00:00

Hello @Andrea Longhitano

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thanks,
Suchitra.
Suchitra Suregaunkar 16,780 Reputation points Microsoft External Staff Moderator

2026-05-26T04:21:08.2066667+00:00

Hello @Andrea Longhitano

Thank you for the upvote.

We are glad that the provided information helped you. Along with that Accepting the answer is equally important because it confirms the resolution and helps others in the community quickly find verified solutions. It also reflects the success of our joint effort to resolve your query. If anything is still unclear or you need further assistance, please let us know.

We are happy to help.

So, kindly consider marking the answer as Accepted and this helps other community members who may encounter a similar issue in the future.

Thanks,

Suchitra.

Answer 1

In Azure Update Manager, the apparent “random” GUID in the ID is expected behavior for configuration assignments and doesn’t indicate an error.

From the Azure Resource Graph log structure for Update Manager:

ID is the full Azure Resource Manager path of the object.
NAME for records of type <resourcePath>/configurationassignments is documented as “the assignment of maintenance configuration to an Azure or Azure Arc VM” and is a unique GUID for that assignment, not just the friendly name.
The TYPE field configurationassignments indicates that the record represents the link between a VM and a maintenance configuration, not the maintenance configuration resource itself.

For configuration assignments created via ARM/CLI/PowerShell, the resource definition is:

{
  "type": "Microsoft.Maintenance/configurationAssignments",
  "apiVersion": "2020-04-01",
  "name": "string",
  "location": "string",
  "properties": {
    "maintenanceConfigurationId": "string",
    "resourceId": "string"
  }
}

The name of this configurationAssignments resource is not required to match the maintenance configuration name. Azure often generates a unique name by appending a GUID (for example, tagetik-prod-patching-b6fd3589-ff9f-43ef-...) to avoid collisions and to uniquely identify each assignment. That’s why:

The maintenance configuration resource has the friendly name tagetik-prod-patching.
The configuration assignment resource that links this configuration to a VM has a different name/ID that includes a GUID.
Other assignments may appear to have a “clean” name if they were created with an explicit name or via a different flow, which can make the behavior look random.

So the GUID in the configurationAssignments ID is by design: it uniquely identifies the assignment object, not the maintenance configuration itself.

References: