Preview · This help is still growing and will be extended over time.
Microsoft 365 integration
The base integration – permissions, shared mailboxes and troubleshooting
Microsoft 365 is echo's base integration. It is always active and cannot be removed. echo uses it to recognize colleagues and Outlook contacts as callers and to show your communication with a contact – emails, appointments, documents and calls – in the contact cockpit.
The integration needs no connection per user. An administrator grants the permissions once for the whole organization (admin consent), usually during the initial setup. After that, echo accesses Microsoft 365 on behalf of the signed-in user and sees only what that user may see in Microsoft 365.
The settings are in two places:
- Settings → Microsoft 365 (administrators only): Permissions re-grants the admin consent; Call History: Voice applications is shown when call queues are enabled for your organization, see Call queues.
- Settings → My accounts (every user): the Shared Mailboxes in the Microsoft 365 section. Each user maintains their own list.
What echo uses from Microsoft 365
Permissions (admin consent)
When you grant consent, Microsoft shows the full list of permissions echo requests. In echo, the request is summarized like this:
- Your profile and contacts – to identify callers
- Calendar events – to show relevant meetings and appointments
- Files and documents – related to your contacts and meetings
- Email information – to provide context about your communications
- Call records – to provide information about your calls
Good to know:
- Almost all access is delegated: echo acts on behalf of the signed-in user and sees only that user's data plus the shared mailboxes the user has access to.
- Call records are read with an application permission, because Microsoft Graph offers Teams call records only that way. echo uses them for the call history and the timeline.
- Consent must be granted with an administrator account and applies to all users. You can review the granted permissions at any time in the Microsoft Entra admin center under Enterprise applications.
Grant the permissions again
Re-grant the consent if Microsoft 365 data is missing in echo, if echo shows Missing Permissions, or after an echo update that needs additional permissions.
Open the permissions
Sign in to echo with an administrator account and open Settings → Microsoft 365. Scroll to Permissions.
Grant consent
Click 1 Grant Microsoft 365 Permissions. A Microsoft window opens. Sign in with an account that may grant admin consent, review the permissions and confirm with Accept.
If Dynamics 365 is added as an integration, echo then asks for the Dynamics consent as well; confirm it in the same way.
Check the result
The button turns green when consent was granted. If echo shows Error! instead, the consent was cancelled or your account may not grant admin consent; try again with a suitable account.
Shared mailboxes (per user)
Your personal mailbox is always included. If you also work with shared mailboxes such as info@ or support@, add them so that echo searches their contacts, emails and appointments too.
- Open Settings → My accounts.
- In the Microsoft 365 section, under Shared Mailboxes, enter the address 1 and click Add.
- To stop using a mailbox, click Remove next to it.
The list is personal: each user maintains their own. Your Microsoft 365 account must have access to the mailbox; echo does not grant any access itself.
Troubleshooting
The call history shows Missing Permissions. The permission for call records has not been granted yet. An administrator clicks Grant Permissions there, or Grant Microsoft 365 Permissions under Settings → Microsoft 365.
Emails, appointments or documents are missing in the timeline. If Microsoft 365 denies access, echo leaves out that part and still shows the rest. Grant the permissions again as described above. Also check that the user has a Microsoft 365 license with a mailbox.
Nothing from a shared mailbox appears. Check the spelling of the address under Shared Mailboxes and that the user really has access to the mailbox in Outlook.
A colleague or contact is not recognized as caller. Check that the phone number is stored on the person in Microsoft 365 or in the Outlook contact. Numbers without a country code are interpreted with the default phone number region.
Consent fails. Only certain administrator roles may grant admin consent for the whole organization. Ask an administrator with that right, for example a Global Administrator, to grant it.
See also: How integrations work · Initial setup