Microsoft Identity Manager
A family of Microsoft products that manage a user's digital identity using identity synchronization, certificate management, and user provisioning.
763 questions
Moving from Delegated Authentication to Service Principal Name (SPN)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 85%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
Tomas Humberto Montiel Alcantara
0
Reputation points
Due to MFA enforcement on the 15th of March, the current delegated authentication setup will no longer be usable. Therefore, the goal is to transition to Service Principal Name (SPN) for authentication, specifically for Workload Identities.
There is an application that requires access to specific information within Teams, excluding sensitive data such as HR information. It has been observed that while granular access is possible in tools like SharePoint, Teams does not provide this level of granularity; it only allows for all or no access to data.
Is there a workaround to achieve this level of access granularity in Teams while maintaining least privilege access for the application using SPN?
Sign in to answer