| Announcement ID | MC791115 | Published Date | 05-08-2024 | |
| Service | SharePoint | Last Updated | 06-06-2024 | |
| Category | Stay informed | Expiration Date | 08-19-2024 | |
| Roadmap ID | 393336 | Action Required by Date | ||
| Tags | Admin impact, New feature, User impact | |||
| Summary |
|---|
| Microsoft Syntex is introducing a new prebuilt model for identifying and optionally extracting sensitive information from SharePoint document libraries, with a rollout beginning in mid-June 2024 and completing by mid-July 2024. Users should be informed about this update. |
| More Information |
|---|
Microsoft Syntex will soon deliver a new sensitive information prebuilt model that can identify and optionally extract sensitive information from files stored in a Microsoft SharePoint document library. When this will happen: General Availability (Worldwide) We will begin rolling out in mid-June 2024 (previously late May) and expect to complete by mid-July 2024 (previously late June). How this will affect your organization: Users will be able to create and apply a model to detect and optionally extract sensitive information from files created or uploaded to the SharePoint document library. If you already have prebuilt models enabled, this new model option will show up automatically. You should communicate with your users about this new sensitive information processing model. Once enabled, users will be able to create a sensitive information model from the model creation panel: After creating the model, they can select languages and sensitive information entities to detect, select sensitive information they want to extract, test the model, and apply it to a SharePoint library. Entities detection Entities extraction selection Library view with detection and selected extraction What you need to do to prepare: After this feature has rolled out, you can manage its availability to your users in the Microsoft 365 admin center. This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. |
