Repository navigation
Please update this page - documentation for bulk user profile update and Taxonomy terms operations #9764
Description
As the ACS service is deprecated, please provide the details documentation how bulk user profile update can be done using Entra ID authentication and what scope required.
Similar for taxonomy automation - how to move terms/enable-disable terms operations can be done using app only permissions by registering the app in the Microsoft Entra ID.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 35a3017a-6d6c-237f-fc57-94247a8f7bf6
- Version Independent ID: 93413445-18fa-9245-ea64-1c1d789dce1e
- Content: Granting access using SharePoint App-Only
- Content Source: docs/solution-guidance/security-apponly-azureacs.md
- Service: sharepoint-online
- GitHub Login: Vesa Juvonen (@VesaJuvonen)
- Microsoft Alias: vesaj
Activity
Ashlesha-MSFT commentedon Jun 16, 2025
Hello Manjit Jagtap (@jagtapm1),
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Ashlesha-MSFT commentedon Jun 16, 2025
Manjit Jagtap (@jagtapm1),
You're absolutely right that with the deprecation of ACS, there’s a growing need for updated documentation that covers these scenarios using the modern Azure AD app-only model. We'll raise this as a documentation gap internally
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.