Skip to content

How to identify AzCosmosDBSqlRoleAssignment unknown/orphan/not-in-use roleAssignmentId's #27464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
babu-kandyala opened this issue Mar 27, 2025 · 1 comment
Labels
CosmosDB customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@babu-kandyala
Copy link

Description

Need to find AzCosmosDBSqlRoleAssignment unknown/orphan/not-in-use roleAssignmentId's and clear it.

Script or Debug output

Environment data

Module versions

Error output

@babu-kandyala babu-kandyala added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 27, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported needs-triage This is a new issue that needs to be triaged to the appropriate team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Mar 27, 2025
@isra-fel isra-fel added CosmosDB Service Attention This issue is responsible by Azure service team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Apr 8, 2025
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @kushagraThapar, @simplynaveen20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CosmosDB customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants