Azure AI + machine learning built-in role

Cognitive Services LUIS Writer

Formerly provided LUIS read, test, and authoring access while excluding application deletion, movement, publishing, settings, and Azure-account changes. LUIS authoring and runtime endpoints are fully retired as of March 31, 2026, and requests fail. This overlay is retained only for migration and access cleanup; it is not a recommendation for a new assignment.

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: 6322a993-d5c9-4bed-b113-e49bbea25b27

Control-plane actions (3)

Data-plane actions (1)

Excluded actions (6)

Assignable scopes (1)

Practical scope

Azure role assignments apply at the selected scope and are inherited by child scopes. Use the narrowest supported resource, resource-group, subscription, or management-group scope that contains the intended resources. Existing assignments for this retired service must be removed at the scope where they were created; an inherited assignment cannot be removed from a child resource.

Common use cases (2)

Prerequisites (2)

Best practices (4)

Security considerations (2)

Assignment guidance

Do not assign this role. Locate existing assignments in Access control (IAM), confirm the retired workload no longer depends on them, and remove each assignment at its originating scope. Reassess access separately for the replacement service.

Common questions

When should I assign the Cognitive Services LUIS Writer Azure role?

Assign Cognitive Services LUIS Writer when you need to: Inventory principals and automation that still hold this legacy role before migration or cleanup begins. Export any recoverable LUIS application data and rebuild the workload in Conversational Language Understanding or a current Microsoft Foundry offering; select current roles for that replacement independently.; and Remove stale direct or inherited assignments after the replacement workload and rollback plan have been verified.. Practical scope: Azure role assignments apply at the selected scope and are inherited by child scopes. Use the narrowest supported resource, resource-group, subscription, or management-group scope that contains the intended resources. Existing assignments for this retired service must be removed at the scope where they were created; an inherited assignment cannot be removed from a child resource.

What permissions does the Cognitive Services LUIS Writer Azure role grant?

The role definition grants 4 combined control-plane and data-plane actions. Representative operations include: Microsoft.CognitiveServices/*/read; Microsoft.Authorization/roleAssignments/read; Microsoft.Authorization/roleDefinitions/read; and Microsoft.CognitiveServices/accounts/LUIS/*. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Cognitive Services LUIS Writer Azure role?

Key considerations when assigning Cognitive Services LUIS Writer: The legacy DataActions could change LUIS application training content even though production publication and deletion were excluded.; and A stale parent-scope assignment remains inherited by child resources until it is removed at the originating scope.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (6)

Official Microsoft Learn documentation →