Skip to main content
Connect Microsoft Teams with June to receive notifications as Adaptive Cards, mirror agent request activity into a Teams channel, and let employees chat with June from Teams.
Microsoft Teams is a communication channel. June uses it to send notifications, post live-progress cards for agent requests, and (optionally) respond to employees who message June. It does not manage devices or import tickets.

​
What you’ll accomplish

  • Grant admin consent for the June app in your Microsoft tenant
  • Install the June bot in the team you want to use
  • Choose the team and channel June posts notifications to
  • Decide whether to mirror agent request activity and enable employee chat

​
Prerequisites

Before starting the integration, ensure you have:
  • A Microsoft Entra (Azure AD) admin who can grant tenant-wide admin consent
  • Permission to install apps into the Microsoft Teams team you want to use
  • June organization admin permissions
Microsoft Teams relies on your Microsoft tenant. If you have already connected Microsoft Entra in June, your Tenant ID is filled in automatically; otherwise it is captured during admin consent.

​
How June Works with Teams

When you connect Teams, an administrator grants consent for the June app in your tenant. June then:
  • Reads the list of teams and channels so you can pick where notifications go
  • Maps employees to Teams users from your directory, so notifications and chat reach the right person
  • Posts notifications and live-progress Adaptive Cards to the channel you select
  • Optionally answers employees who message or @mention June

​
Capabilities

​
Channel options

After connecting, you control two behaviors:

​
Setup Process

1

Start the connection from June

  1. Log into June
  2. Navigate to Settings → Integrations
  3. Select Microsoft Teams from the available integrations
  4. Click Connect to begin the Microsoft consent flow
2

Approve the June app

  1. Sign in with a Microsoft account that can grant admin consent for your tenant
  2. Review the permissions June requests—listing teams and users, and posting messages to channels
  3. Click Accept to grant consent for your organization
Admin consent must be granted by a tenant administrator. If you are not an admin, the consent screen will ask you to request approval from one before you can continue.
3

Return to June

Microsoft redirects you back to June and your Tenant ID is recorded. The connection is now associated with your Microsoft tenant.

​
Step 2: Install the June Bot in Your Team

The June app must be present in the specific team you want notifications in, so it has permission to post there.
1

Add June to the team

  1. In Microsoft Teams, open the team you want to use
  2. Go to Manage team → Apps → More apps
  3. Find the June app and add it to the team

​
Step 3: Choose a Team and Channel

1

Select where notifications go

  1. In June’s Teams integration settings, choose the Team from the dropdown
  2. Choose the Channel within that team for notifications
  3. Save your selection
Confirm a test notification card appears in the channel you selected.

​
Step 4: Configure Behavior

1

Request mirroring

Leave Mirror request executions into the Teams channel on for a live feed of agent activity, or turn it off so the channel only receives notifications.
2

Employee chat (optional)

Turn on Allow employees to chat with June via @mention to let employees message or @mention June for help directly in Teams. Leave it off to keep June admin-only.

​
Example Use Cases

Keep request mirroring on so your IT channel sees an Adaptive Card for every request June works on, updated live as it progresses.
Point notifications at a dedicated channel so the right team sees June’s updates in the tools they already use.
Enable employee chat so staff can ask June questions about their devices, requests, or policies without leaving Teams.

​
Troubleshooting

Solutions:
  • Confirm admin consent was granted for your tenant during connection
  • Verify the connection status shows Active; reconnect if it doesn’t
  • If you connected Microsoft Entra separately, confirm it is still connected so the Tenant ID stays valid
Symptoms: June can list teams but posting failsSolutions:
  • The June bot must be installed in the specific team you selected—add it via Manage team → Apps
  • Re-select the team and channel after installing the app
Solutions:
  • Confirm Allow employees to chat with June via @mention is turned on
  • Make sure the June bot is installed in the team or chat where the message was sent
  • Check that the employee’s directory account uses the work email June has on file
Solutions:
  • Tenant consent may have been revoked in Microsoft Entra—reconnect from June’s Teams settings
  • Confirm the June app hasn’t been removed from your tenant or team

​
Security Best Practices

  • Tenant-scoped consent: June operates only within the tenant that granted consent, and inbound activity is allowlisted to that tenant
  • Least privilege: June requests only the permissions needed to list teams/users and post notifications
  • Public vs. secret values: Your Tenant ID is a public routing identifier; no long-lived secret tokens are stored—access tokens are minted on demand per tenant
  • Revoke anytime: Remove the June app from a team, or revoke consent in Microsoft Entra, to cut off access immediately

​
Next Steps

Microsoft Entra Integration

Connect Entra so your Tenant ID and employee directory sync automatically

Slack Integration

Prefer Slack? Connect it as an alternative communication channel

Asset Discovery

Connect your asset inventory so June has context for the requests it mirrors

AI Insights

See how June reasons about the requests it reports on

​
Support Resources

Need help with your Microsoft Teams integration?
  • Microsoft Documentation: Review Microsoft’s guide to managing apps in Teams for tenant-level details
  • June Support: Contact support for integration-specific assistance
Once admin consent is granted and the June bot is installed in your team, notifications begin as soon as a channel is selected.