Closed kahawai-sre closed 1 year ago
@kahawai-sre Thanks for your feedback! We will investigate and update as appropriate.
@kahawai-sre I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.
Looking at the documentation for Conditional Access for Workload Identities, it is not clear to me whether CA policy can be enabled for App Registrations aka Service Principals enabled for Federated Credentials. I may be missing something, apologies if that is the case.
Unless this is confirmed elsewhere, can this document or another relevant page please be updated to provide clarity on that question?
Previously I would have been able to validate this in my own tenant using an AAD P2 license, but not now that CA for Workload Identities has shifted to "Advanced" licensing outside of P2 :-)
Many thanks
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.