You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: