Azure Containers built-in role

Azure Kubernetes Fleet Manager Hub Agent Role

Allows the Fleet Manager hub-cluster identity to read service public IP addresses and create, update, or delete Azure Traffic Manager profiles and endpoints for Fleet DNS load balancing. It is a feature-specific service identity role, not a generic provider-managed hub boundary or a human Kubernetes role.

Role-definition permissions are imported from Microsoft Learn. Practical scope, use cases, prerequisites, best practices, security considerations, assignment guidance, and relationships have been reviewed against the official sources below.

Role definition ID: de2b316d-7a2c-4143-b4cd-c148f6a355a1

Control-plane actions (7)

Data-plane actions (0)

None — this role grants no data-plane (data access) actions.

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

For DNS load balancing, Microsoft documents assigning the role to the Fleet Manager system-assigned identity on the resource group where Traffic Manager resources are created and separately on each resource group containing public IP addresses for exported services. Do not assign it generically on the Fleet resource or unrelated parent scopes.

Common use cases (1)

Prerequisites (1)

Best practices (2)

Security considerations (2)

Assignment guidance

Assign Azure Kubernetes Fleet Manager Hub Agent Role to the Fleet Manager system-assigned identity on the dedicated Traffic Manager resource group and on each resource group that contains public IPs consumed by ServiceExport. Use Fleet Contributor or Fleet RBAC roles for people and remove assignments when the DNS load-balancing feature is retired.

Related roles (1)

Editorial sources (6)

Official Microsoft Learn documentation →