Connect Microsoft 365 mail and calendar
Overview
Section titled “Overview”Microsoft 365 integration uses a configured Entra web application and a separate delegated connection for each CRM user. The organization registration defines the allowed capabilities; each user connects their own Microsoft identity. Saving the registration alone neither connects a mailbox nor proves mail/calendar delivery. CRM login remains password/MFA based.
Purpose
Section titled “Purpose”Use this procedure to establish the supported personal mailbox and calendar connection with explicit consent.
Prerequisites
Section titled “Prerequisites”-
Administrator access to CRM integration settings and the intended Microsoft tenant.
-
An approved Entra registration and exact redirect URI for the CRM origin.
-
A durable communication encryption key and a user authorized to consent to the required delegated scopes.
Procedure
Section titled “Procedure”-
In the intended tenant, prepare a web application with the exact callback URI https://crm.example.com/api/microsoft/callback, replacing the example origin with the approved CRM origin.
-
In Settings > Email & communications > Microsoft 365, enter the approved tenant/application registration and enable only the required capabilities. Protect the client secret through the provided configuration process.
-
Have each user open My Microsoft 365 account, connect their own identity and consent to the selected scopes. Verify the connected mailbox before enabling background work.
-
Select the desired mailbox folder and calendar synchronization direction. Start with the narrowest scope required for the business process.
-
Validate a controlled mail or calendar operation and review the CRM attempt/synchronization history and Microsoft-side result.
-
Disconnect or reconnect through the personal page when access is no longer required or consent/configuration changes.
Expected result
Section titled “Expected result”The user has an explicit delegated connection with selected capabilities and independently observed test results.
Important notes
Section titled “Important notes”-
Mail.Send, Mail.Read and calendar permissions serve different operations; avoid granting unused capabilities. The implementation uses the global Microsoft Graph endpoint.
-
Disconnect removes the local token cache; underlying tenant consent is managed in Microsoft.
-
Shared-mailbox/calendar delegation and CRM single sign-on are not established by this connection.
-
Actual tenant acceptance remains an installation-specific test, even when simulator and source tests pass.
Troubleshooting
Section titled “Troubleshooting”-
Reconnect required: review tenant registration, secret expiry and delegated consent, then reconnect.
-
Callback rejected: compare the exact approved redirect URI and tenant/application settings.
-
Permission failure: check the user-selected capability and tenant consent before broadening access.
Related articles
Section titled “Related articles”Search the guides or talk to the ZBIX team.
Software products, application engineering and IT services from Zbix Technologies.
Visit our company website ↗