Microsoft 365: SharePoint, Teams, and Calendar
Connect your own Microsoft 365: an admin approves Current once, then each person connects. What each permission does, and what to do if Microsoft refuses.
Updated 4 min read
On this page · 5 sections
Current connects to your own Microsoft 365 organization. There is nothing to register in Azure on your side: a Tenant Admin approves Current once for the organization, then each person connects their own Microsoft account.
Note
Teams or Slack
A workspace uses Microsoft Teams or Slack for its messages, never both. If your workspace connects Slack, Current stops sending messages to Teams, and email, calendar, SharePoint, To Do and email capture keep working through Microsoft 365 as described here. See "Connect Slack to Current".
| What | Who does it | How often |
|---|---|---|
| Approve Current for the organization | A Tenant Admin, signed in at Microsoft as a Microsoft 365 global admin | Once |
| Connect Teams, Calendar, and To Do | Each person, with their own Microsoft account | Once per person |
| Link a SharePoint folder | A project manager, on the project's page | Per project |
Step 1: approve Current for your organization
- 1Open Settings › IntegrationsMicrosoft 365 is the card pinned at the top of the page, above the chart of tools. It shows whether your organization has approved Current, whether your own account is connected, and a state for each part: SharePoint, Teams, Calendar, To Do and Mail capture.
- 2Choose Approve for my organizationIt is the card's filled button until your organization has approved Current, and only a Tenant Admin sees it. The same button sits under Platform when you press Manage on the card.
- 3Sign in at Microsoft as a global adminUse a Microsoft 365 global admin account from your organization. It doesn't have to be the account you use in Current: if someone else is your Microsoft admin, they type their own sign-in on your screen. Microsoft lists what Current asks for and records the approval for the whole organization.
- 4Come back to CurrentIf staff-mailbox capture isn't on yet, Current first sends you back to Microsoft once more to turn it on (see the note below). The drawer then reads Approved for your organization, SharePoint document storage is on, and nobody on your team is asked to approve anything when they connect. When Current later adds a capability that needs a new permission, a Tenant Admin chooses Re-approve under Platform, signed in as a global admin, and people pick it up the next time their connection refreshes.
Note
Seeing what is working and what is missing
Press Manage on the Microsoft 365 card at the top of Settings › Integrations, or press one of its parts. Under Platform you will find a short list: your organization's setup first, then how many of your connected people have each part working, so you can see "7 of 9" rather than a single tick that hides the other two. Anything Current has not checked yet says so instead of looking broken, and where something needs fixing it tells you what to do. One thing worth knowing: approving Current for your organization and Microsoft granting each permission are two different steps, and it is easy to accept the wrong one. If that happens, this list tells you. Current works all of this out from what Microsoft already tells it while syncing, so it never asks for extra access just to check, and when you approve something new nobody has to reconnect.
Note
Reading every staff mailbox
Microsoft's approval screen also lists reading mail across your organization. That is staff-mailbox capture, which brings in client email from your colleagues' mailboxes, including people who don't use Current. It turns on when a global admin approves from inside your workspace. On the second trip to Microsoft (it may ask you to pick the account again), Current checks two things with Microsoft: that the account is a global admin or Privileged Role Administrator, and that your organization owns the email domain of the Tenant Admin who started the approval. Which mailboxes it covers: everyone in your workspace, plus staff from your PSA whose email address is on one of the domains Microsoft has verified for your organization, so if your staff use a second domain, verify it with Microsoft and they are included. Each mailbox then brings in its client email from the past 12 months. Approving is not quite the last step: Microsoft also has to grant the mail permission itself, and it is easy to accept the wrong one, so if the Microsoft 365 card or the Staff mailboxes list says mail access hasn't been granted, approve again and accept the application permission rather than the delegated one. Only mail to or from a client's domain is stored, and a Tenant Admin can switch any mailbox off in Users & roles, under Staff mailboxes. If your organization has already approved Current and capture is still off, a Tenant Admin chooses Turn on staff-mailbox capture under Platform, signed in as a global admin. Until capture is on, email history on the CRM timeline comes from each person's own connected mailbox.
Step 2: everyone connects their own account
- 1Choose Connect your accountIt is the filled button on the Microsoft 365 card at the top of Settings › Integrations. If you don't see that page, open Settings › Your settings › Microsoft 365 and choose Connect Microsoft 365 on the Microsoft Teams & Calendar card. Microsoft suggests the account that matches your Current email. Sign in with your work account from your own organization, and Microsoft sends you back to Current connected. If you pick an account from a different organization than the rest of your workspace, Current still connects it and tells you so.
- 2Map projects to channelsA PM maps each project to a Teams channel. Every comment, note, or chat added in Current posts to that channel, Teams stays the source of truth for project communication. Partner comments arrive attributed as "Partner: [name]".
- 3Let Calendar work both waysTask due dates and milestones push to your calendar; Current reads your busy blocks so scheduling respects real availability.
- 4Get your to-dos and project tasks in Microsoft To DoThe same connection also puts your personal to-dos (both ways), and your assigned project tasks (a one-way, personal view. Checking one off there never completes the real task) into Microsoft To Do. It turns on automatically once you connect. Nothing extra to set up here. See "Microsoft To Do two-way sync: your to-dos and project tasks".
Once your organization has approved Current, a project manager pastes a SharePoint folder link on a project's page. Documents then attach to tasks as links, and each person opens them with their own Microsoft access.
Note
Your files never move
Current stores document titles and links only. The actual files stay in your SharePoint, and Current never copies them into its own storage.
If Microsoft stops you
| What you see | What it means | What to do |
|---|---|---|
| Need admin approval (AADSTS90094 or AADSTS65001) | Your organization hasn't approved Current yet | A Tenant Admin runs Step 1, signed in as a Microsoft 365 global admin |
| Selected user account does not exist in tenant (AADSTS50020) | Current sent the sign-in to the wrong Microsoft directory. Fixed on September 11, 2026 | Choose Connect again |
| The signed in user isn't assigned to a role for the app (AADSTS50105) | Your organization only lets assigned people use Current | Your Microsoft 365 admin assigns you to the Current app in Microsoft Entra, under Enterprise applications |
| Access has been blocked by Conditional Access policies (AADSTS53003) | A sign-in policy in your organization stopped it | Your Microsoft 365 admin checks the Entra sign-in logs for the policy that applied |
| Staff-mailbox capture isn't on yet: the account isn't a global admin | The account that signed in for the check holds neither the Global Administrator nor the Privileged Role Administrator role | Choose Turn on staff-mailbox capture under Platform and sign in at Microsoft as a global admin |
| Staff-mailbox capture isn't on yet: your organization doesn't own your email domain | The Microsoft 365 organization you signed in to doesn't list the domain of your Current email among its verified domains. This is what stops an account in a client's organization from turning capture on for your workspace | A Tenant Admin whose Current email is on your organization's own domain starts the approval, signed in as a global admin of that organization. If you have just added that domain to Microsoft 365 and verified it, choose Re-approve under Platform afterwards so Current checks again |
| Staff-mailbox capture isn't on yet: already linked to another workspace | Each Microsoft 365 organization feeds one Current workspace. This one is already linked to another, or your workspace is linked to a different organization | Contact Current support, who can move the link |
For the approval, assignment and sign-in-policy rows, the Microsoft 365 card shows the same next step when Microsoft sends you back to Current. The staff-mailbox rows appear as a message when Current brings you back to Integrations.
The exact Graph permissions
Each person (delegated) openid profile email offline_access User.Read # sign-in and staying connected ChannelMessage.Send ChannelMessage.Read.All # post to project channels, read replies Team.ReadBasic.All Channel.ReadBasic.All # the team and channel picker Channel.Create # a channel for each new project Chat.Create Chat.ReadWrite # notifications as a Teams chat ChannelMember.Read.All User.ReadBasic.All # who is in a project channel, finding a teammate in Teams Calendars.ReadWrite Calendars.Read.Shared # your calendar, teammates' free/busy MailboxSettings.Read # your time zone Files.Read.All # a SharePoint folder linked to a project Tasks.ReadWrite # Microsoft To Do sync Mail.Read Mail.ReadWrite # client email history, replies from it, bounce notices Mail.Send Mail.Send.Shared # sequences and email-history replies from your own mailbox; sequences from a shared one Your organization (application, listed on the approval in Step 1) Mail.Read Mail.ReadWrite # staff-mailbox capture (on once a global admin approves; see Users & roles)
Note
Tagging people in Teams needs two newer permissions
ChannelMember.Read.All and User.ReadBasic.All let Current check who is in a project's Teams channel and find a teammate's Teams account from their email address. If your organization approved Current before these two were added, a Microsoft 365 global admin approves again: a Tenant Admin presses Manage on the Microsoft 365 card at the top of Settings › Integrations and chooses Re-approve under Platform, signed in at Microsoft as a global admin. Until then, a person tagged in a comment gets a Teams chat or an email instead of a tag in the channel. Nobody reconnects: each person's Microsoft connection picks up the new permissions on its next refresh. "How Teams channels work inside projects" explains the rest.
Tip
Channel picker showing nothing?
Listing a team's channels needs your organization's approval to include Channel.ReadBasic.All. If the picker is empty, a Tenant Admin chooses Approve for my organization under Platform (Re-approve once it's approved); until then, paste the team and channel IDs from the channel's Get link in Teams.
Was this helpful?
← Previous
Connect Autotask and choose what syncs
Next →
HubSpot: connect, import your book, and keep it in step