Importing people
Dynasend can create and update signatures from your directory or from a spreadsheet. Pick the path that matches how your IT team already works.
Choose a method
| Method | Best when | Docs |
|---|---|---|
| Microsoft 365 directory | A Global Administrator can grant consent and you want Dynasend to pull Entra users and groups | Microsoft 365 directory sync |
| Azure SCIM | You already provision apps with SCIM, or you need Entra-side scoping and push schedules | Entra ID / SCIM |
| Google Workspace directory (Coming Soon) | You sync people from Google Directory via Connectors | Google Workspace directory |
| CSV bulk import | You need a one-time or occasional roster load for a program | CSV bulk import |
Running more than one source
You can connect Microsoft 365 directory and Azure SCIM on the same account. When both cover the same email, SCIM owns that signature. Directory sync still stores Entra person and group data.
Prefer one continuous directory source per population unless you intentionally keep SCIM for a subset of users.
Deploying signatures is separate
Importing people fills the roster. Getting signatures onto mail is covered under:
Form field mapping and precedence for directory values are configured in Form setup.