Enterprise rollout is smoother when your organization tests identity, roles, repository access, and document saves with a pilot group before expanding access.
Recommended rollout sequence
- connect Microsoft Entra and confirm admin consent
- set allowed domains, default roles, and any required role mappings
- connect Microsoft 365 repositories and sync locations
- approve a small set of repository locations
- run a pilot with a small number of users and matters
- expand only after the pilot has completed real matter work successfully
What to test during a pilot
- a new user can authenticate through Entra
- the user receives the expected organization role
- the user can see only approved repository locations
- a matter can be linked to a repository successfully
- a document can be saved once and then versioned successfully
Troubleshooting identity issues
- Consent completed but setup failed: verify that the returned tenant matches the one used when the request began
- User cannot access the organization: review allowed domains, default role, and any required role mappings
- SSO enforcement causes unexpected lockout: confirm pilot users are authenticating through the intended Microsoft tenant before enforcing sign-in broadly
Troubleshooting repository issues
- Locations do not appear: verify Microsoft 365 consent and run a location sync again
- Users can see too many locations: tighten the allowlist and leave only approved libraries enabled
- Documents cannot save: confirm the matter is linked to an allowed location and that the integration is still connected
- Versioning fails: save the document to Microsoft 365 once before creating a new version
Operational questions to settle early
- who manages Entra changes when staff join or leave
- who approves new repository locations for use
- who supports pilot users during rollout week
- when SSO enforcement should move from optional to required
When to contact support
Contact Divorcepath support if admin consent is returning errors, if Entra users are not receiving the expected access, or if repository saves fail after the matter is linked to an approved Microsoft 365 location.
