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

in IIS manager UI, you cannot use Azure AAD EntraID? #34784

Open
3 tasks
Rick-Anderson opened this issue Feb 21, 2025 · 0 comments
Open
3 tasks

in IIS manager UI, you cannot use Azure AAD EntraID? #34784

Rick-Anderson opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
reQUEST Triggers an issue to be imported into Quest

Comments

@Rick-Anderson
Copy link
Contributor

Rick-Anderson commented Feb 21, 2025

Fix: add a note to

that states the User Name must be a local or Windows Active Directory user and not a Microsoft Entra ID to this page. Make an include file we can easily add/edit.

Image Image Image

Once the Shared configuration uses Azure AAD EntraID, the UI allows you to do so, but w3svc and WAS cannot be started after that.

The app pool identity also allows Entra ID be input and customer even has web apps running with that. But as the document requires, that needs the GPOs list in the doc and those cannot even be assigned to the EntraID and so we do not know what problem it will be later.

I think this could become more and more common later since customers are moving to Azure. If we can have a clear document states those areas IIS Management console cannot use Azure AAD EntraID, it can avoid a lot of arguments from customers.

contact Jason Xu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reQUEST Triggers an issue to be imported into Quest
Projects
Development

No branches or pull requests

1 participant