Skip to main content

Microsoft 365 directory sync

Microsoft 365 directory sync pulls people and groups from Entra ID into Dynasend. A Microsoft Global Administrator grants consent once. Mailbox users never grant access. Dynasend never writes data back to Entra ID.

Use this connector when you want directory sync without building an Azure enterprise app and SCIM provisioning job. For enterprise SCIM push, see Entra ID provisioning.

Before you start​

  • You need a Microsoft 365 subscription and an Entra tenant.
  • A Global Administrator for that tenant must complete Connect.
  • Your Dynasend role must allow Connectors access (typically Owner or Developer).
  • After Connect, set a default program (and location, if your program uses locations) so new signatures land in the right place.

Connect​

  1. Sign in at https://login.manage.dynasend.net/.
  2. Open Connectors.
  3. In Microsoft 365 directory, click Connect.
  4. Sign in as a Global Administrator when Microsoft prompts you, and accept the consent screen.
  5. When you return to Dynasend, the connector status shows Connected.

Consent covers reading users and groups for signature sync. End users do not see a consent prompt.

Sync users and groups​

After Connect:

  1. On the same Connectors card, click Sync (or open Manage and run sync from the directory).
  2. Dynasend creates or updates directory members and groups, then creates or links signatures by email.
  3. Open Manage on the connector to review members, groups, last sync time, and default program or location.

Re-run Sync whenever you need a fresh pull. Scheduled sync may also run in the background for connected accounts.

Group membership includes direct Entra group members only. Nested groups and dynamic membership expansion are not resolved in this version.

Defaults and routing​

On the Microsoft 365 directory manage page you can:

  • Set the default program and default location for new signatures.
  • Add program routing and location routing rules so groups or other directory attributes map users to the correct program or office.

Map signature form fields to directory attributes in Form Builder. Use the Microsoft 365 directory mapping and precedence options — not the SCIM mapping fields. Those controls appear when Microsoft 365 directory is connected. See form setup.

Disconnect​

Click Disconnect on the Connectors card when you want Dynasend to stop pulling from Entra ID.

  • Consent for directory sync is cleared.
  • Existing signatures stay in Dynasend.
  • Commercial Outlook SSO tenant linking is separate; disconnecting directory sync does not remove that link by itself.

If Azure SCIM is also connected​

You can run Microsoft 365 directory sync and Azure SCIM provisioning on the same account.

When both cover the same email address, SCIM owns the signature. Directory sync still stores the Entra person and group data, but it does not take over that signature from SCIM.

Prefer one directory source per account unless you intentionally keep SCIM for a subset of users.

Microsoft 365 directory vs Azure SCIM​

Microsoft 365 directoryAzure SCIM
How data arrivesDynasend pulls from Microsoft Graph after administrator consentEntra pushes users and groups to Dynasend
SetupConnectors → Connect as Global AdministratorCreate a SCIM server, then configure provisioning in Entra
Best fitMid-market accounts that want Google Workspace–style syncEnterprise accounts that already run SCIM provisioning
Form mappingMicrosoft 365 directory mapping fieldsSCIM mapping fields

Both paths are one-way: Entra ID → Dynasend.