Choose your directory import scope.
Synchronize eligible users and groups, across your directory or a selected Entra security group.
Review supported file exposure with the people who own the work. Confirm which access is still needed, remove an eligible permission without Purview setup overhead, and check the result in Microsoft. SharePoint and OneDrive protection use separate connections from directory sync.
Directory sync · Separate OneDrive, SharePoint, and Teams connections
Capabilities
Synchronize eligible users and groups, across your directory or a selected Entra security group.
Connect OneDrive and SharePoint in minutes to review sharing and remove eligible item permissions.
Enable the separate Teams connection to send employees security notifications.
Native controls
Sharing policy, a permissions snapshot and a business owner’s decision serve different purposes. Keep the native controls you need and evaluate how Elba helps your team review supported exposure and eligible corrections.
| Control or workflow | Question it helps answer | What to evaluate |
|---|---|---|
| Native external-sharing settings | Which external audiences may receive access? | Check organization and site settings together; the more restrictive setting applies. Review the item’s permissions as a separate step.Microsoft’s external-sharing guidance |
| Native permissions snapshot | Which sites have broad permissions or sharing links? | Check SharePoint Advanced Management availability, the report date and excluded sites. A snapshot helps choose a review scope; it is not proof that a later correction worked.Microsoft’s site-permissions report |
| Restricted Content Discovery | Should a SharePoint site be temporarily harder to discover in Copilot? | Check the current license requirements. This SharePoint control leaves existing permissions in place and does not cover OneDrive; check access separately.Microsoft’s discovery-control boundaries |
| Elba sharing review | Does this supported exposure still serve a business need? | Review the finding with its owner, choose an eligible correction and verify the result. Keep unsupported or unresolved access visible. |
Example workflow
How the integration supports a specific security task.
Start with a supported SharePoint or OneDrive finding. Identify the item, permission and available owner context, and retain the observation date and coverage limits.
Ask the owner which collaborators still need access. Record the decision and any exception before changing a link or permission.
Apply an eligible permission-removal action when Elba exposes it. Verify the intended access change and necessary collaboration in Microsoft, including any remaining inherited or group access.
Demo agenda
Agree a representative scenario with our team. Findings and actions depend on the active connection and object. Directory sync alone does not inspect files, and the demo does not require changing your production permissions.
Related capability
Before you connect
The Microsoft 365 base connection synchronizes directory data. Teams notifications, phishing simulations, and SharePoint or OneDrive Data Protection use separate Microsoft applications or consent flows.
Explore security & privacyUse a Global Administrator for the complete flow. Some tenant-wide permissions require that role even when an Application Administrator is recognized during part of sign-in.
No. It limits which directory records elba queries and stores, while the application permissions accepted during tenant consent remain tenant-wide.
Not after administrator consent. Choose and validate the intended import boundary before authorizing the connection.
No. Elba connects directly through Microsoft Graph and SharePoint/OneDrive OAuth consent flows without requiring Microsoft Purview DLP rule authoring or E5 compliance add-ons.
No. These capabilities use separate applications or consent flows and must be reviewed and enabled independently.
Discuss your requirements
Walk through a supported SharePoint or OneDrive finding, the owner’s decision and the evidence to check after an eligible correction. Confirm the required connections and remaining access paths before choosing your next step.