Skip to content
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

Non AAD User entities are always added to ADLS Gen2 ACLs as Groups #1049

Closed
MRayermannMSFT opened this issue Jan 7, 2019 · 1 comment
Closed
Assignees
Labels
🪲 bug Issue is not intended behavior ⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2)
Milestone

Comments

@MRayermannMSFT
Copy link
Member

Contrary to what we were told by the ADLS Gen2 team, non AAD User entities should not always added to ADLS Gen2 ACLs as Groups. Instead, only AAD Groups should be added as groups, while service principals/applications/etc. should be treated as users.

@MRayermannMSFT MRayermannMSFT added 🪲 bug Issue is not intended behavior ⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2) labels Jan 7, 2019
@MRayermannMSFT MRayermannMSFT added this to the 1.6.2 milestone Jan 7, 2019
@MRayermannMSFT MRayermannMSFT self-assigned this Jan 7, 2019
@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Jan 7, 2019
@MRayermannMSFT MRayermannMSFT moved this from Committed to In Progress in Storage Explorer Jan 7, 2019
@MRayermannMSFT MRayermannMSFT moved this from In Progress to Done in Storage Explorer Jan 7, 2019
@MRayermannMSFT
Copy link
Member Author

Fix merged into hotfix branch.

@craxal craxal removed this from Done in Storage Explorer Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Issue is not intended behavior ⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2)
Projects
None yet
Development

No branches or pull requests

1 participant