Integrations

Microsoft Teams

Get DevStride notifications as personal Microsoft Teams messages: an administrator connects your Microsoft 365 organization and makes the app available, then each person adds the app, chooses what to receive and sends themselves a test.

DevStride can send your mentions, the item activity you choose and your due-date reminders as personal messages from the DevStride app in Microsoft Teams. Messages arrive in a one-to-one chat with the app, never in a team channel.

Who does what

StepWhoHow long
1. Connect your Microsoft organizationA DevStride member with Manage Integrations, after a Microsoft 365 administrator approves DevStride onceA few minutes
2. Make the app available in TeamsYour Teams administratorA few minutes, then up to a few hours for Teams to show it
3. Add the appEach person who wants Teams notifications, or an administrator for chosen peopleOne minute
4. Choose notificationsEach person, in DevStrideOne minute
5. Send yourself a testEach person, in DevStrideOne minute

Before you start

  • In DevStride, connecting needs the Manage Integrations permission. Everyone who wants Teams messages needs an active membership and a verified email address: DevStride sends nothing to an unverified address, not even a test.
  • In Microsoft, an administrator who can approve apps, such as a Global Administrator or Cloud Application Administrator, approves DevStride once for your organization.
  • In Teams, each person signs in with a work or school account in that organization and has a license that includes Teams. Personal accounts (Outlook.com, Hotmail) cannot be used.
  • Matching email: each person signs in to Teams with the same email address as their verified DevStride account. DevStride recognises you in Teams by email, so a Microsoft sign-in that matches no DevStride member gets no notifications.

You do not create an Azure bot, register an app in Microsoft Entra, or handle any secret. Connecting Teams does not change how anyone signs in to DevStride.

For administrators

Connect your Microsoft organization

Do this once per DevStride organization.

  1. In DevStride, open Configure Settings → Integrations → Microsoft Teams. The page guides you through three steps.
  2. 1. Microsoft 365 administrator approval. Pick the option that describes you:
    • I'm a Microsoft 365 administrator: you will approve DevStride during the connection. When Microsoft asks, tick Consent on behalf of your organization before you accept, so other people can connect later without asking you.
    • Our administrator has already approved DevStride: carry on with your own work account.
    • I need to ask our administrator: they can connect from this page themselves, or you start the connection and, if your organization allows it, Microsoft offers a button to request their approval.
  3. 2. Sign in with your work account. Use the work account of the Microsoft 365 organization whose Teams should receive the messages. If Microsoft signs you straight in with a different account, sign out of Microsoft in this browser first, or use a private window.
  4. 3. Connect. Select Connect Microsoft Teams and finish Microsoft's sign-in and approval in the same browser. Each approval link works once and expires after one hour.

The first approval in a Microsoft organization adds two enterprise applications to its Microsoft Entra admin center: DevStride Teams Integration (the sign-in) and DevStride Teams Connection Authorization (the administrator-only permission DevStride checks). Both come from the same single approval; leave both in place.

Back in DevStride, the page says Microsoft Teams is connected. Under Connected Microsoft Tenant, check the organization name, the Microsoft tenant ID and the DevStride environment. If it is the wrong organization, select Remove, sign out of Microsoft in this browser and connect again.

Make the app available in Teams

The DevStride app is not in the public Teams Store: you add it to your organization's own app catalog from a package that DevStride gives you.

  1. On the same DevStride page, under Getting the DevStride app to your users, select Download the DevStride Teams app. You get a ZIP file (for example devstride-teams-1.0.7.zip). Keep it zipped: you upload the ZIP itself. It holds a manifest and icons, no secrets.
  2. A Teams administrator uploads it, in either place:
    • Teams admin center: admin.teams.microsoft.com → Teams apps → Manage apps → Upload new app. Then open DevStride on the Manage apps page to choose who can use it.
    • Teams itself: Apps → Manage your apps → Upload an app → Upload an app to your org's app catalog.
  3. In Teams, open Apps → Built for your org and check that DevStride is listed. New catalog apps can take a few hours to appear.

The package belongs to the DevStride environment you downloaded it from and only delivers that environment's notifications. Production customers download it from app.devstride.com.

Install the app for people

Optional. Instead of each person adding the app in Teams, DevStride installs it for the people you pick. It does not change anyone's notification choices. You need Manage Integrations, and your organization must already be connected (step 1) with the app in your catalog (step 2). The section is on the same page: Configure Settings → Integrations → Microsoft Teams → Install the app for people.

  1. Microsoft 365 administrator approval. This is a second, separate approval: it lets DevStride install its own app, and nothing else, for people in your Microsoft organization. Select Approve in Microsoft; a Microsoft 365 administrator signs in and accepts. Microsoft brings you back to this page, which then shows Approved. If it still says Not approved yet, wait a minute and reload: Microsoft can take a moment to apply a new approval.
  2. Teams App ID. In the Teams admin center, open Teams apps → Manage apps → DevStride and copy its App ID. (This is the ID your catalog gave the app, not the one inside the package.) Paste it into Teams App ID and select Save. Your catalog needs DevStride app package 1.0.6 or later; if yours is older, download the current package and upload it again first.
  3. Choose people. Select Choose people…, pick up to 25 members and select Choose. The list shows the Microsoft sign-in name DevStride will use for each person: their DevStride email address. Check it, then select Install for N people.

Each person gets a result:

ResultWhat it means
InstalledThe app is in their Teams. Teams tells DevStride where to send their messages once it appears, which can take a minute.
Already installedNothing to do.
Not foundTheir DevStride email is not a Microsoft sign-in name in your organization. They can add the app themselves. If everyone comes back as not found, check the saved App ID.
Microsoft refused it for this personUsually a Teams app policy blocks DevStride for them, they have no Teams license, or Teams is turned off for them. If everyone is refused, upload the current app package and try again.
Not approvedThe Microsoft administrator approval is missing or was removed.
Not an active member with a verified emailNothing was attempted.
Not attempted / Microsoft asked to waitInstall again for the remaining people a little later. Anyone already installed is reported as such, so repeating is safe.

There is deliberately no "install for everyone" button in DevStride: you choose people, 25 at a time. Installing the app does not turn on any notifications; each person still chooses their notifications.

For everyone who wants Teams notifications

Add the app in Teams

If an administrator installed it for you, it is already in your Teams: skip to step 3 below.

  1. In Teams, check that your profile menu shows your work account.
  2. Open Apps → Built for your org, select DevStride and select Add.
  3. Open the app's chat when Teams offers Open. You can always find it under Chat, or under Apps → Manage your apps.

When the app is added, its chat opens with a Welcome to DevStride message. It explains what the app sends, that it only sends notifications and works in this personal chat only, and has buttons to Open DevStride, Get started (this page) and Contact support. It also tells you whether DevStride recognised you:

  • You are connected. Carry on with Choose your notifications.
  • DevStride could not find an account for your Microsoft sign-in… Your Microsoft sign-in email matches no member of a DevStride organization connected to this Microsoft organization, so no notifications will arrive. Use a DevStride account with that same email address (ask your DevStride administrator to invite it, or use Sign up), then remove the app and add it again.

Adding the app is what tells DevStride where to send your messages. If the app was already there before your organization was connected, remove it and add it again; just reopening it is not enough. Notifications start from the moment the app is added; earlier ones are not sent to Teams later.

Choose your notifications

  1. In DevStride, open your account menu and go to My Account → Notification Settings. Settings save as you change them.
  2. Under Notify Me of Direct Mentions Via, tick Teams to get your @mentions in Teams. It is off by default.
  3. Under Send Conditional Push Notifications To, open the Teams tab and tick the activities you want, for each role you can hold on an item (Assignee, Creator, Watcher, Participant).
  4. On the same tab, the Due date approaching, Due date arrived and Overdue rows are your due-date reminders. Each has a time of day, and approaching and overdue have a number of days; see due date reminders.

Teams works alongside the Notification Center, email and Slack: each channel has its own tab, so the same event can go to several places or only one. If Teams shows (Teams Integration Required), your organization is not connected yet: ask an administrator.

Send yourself a test

In Notification Settings, the Your Microsoft Teams notifications panel checks your setup:

RowWhat it tells you
ConnectedYour organization is connected to Microsoft Teams, and to which Microsoft organization.
App addedYou have added the DevStride app in Teams, so DevStride has a chat to send to. If not, it tells you to add it, or to remove and add it again.
EmailShown only when your DevStride email is not verified yet. Nothing is sent until it is.
TestSelect Send me a test message. The panel says whether Microsoft accepted it, or exactly what is missing.
ReceivedAfter checking Teams, select I got it or It didn't arrive. Only you can confirm: DevStride cannot see whether a Teams message was read.

The test is sent even when all your Teams notifications are still off; the panel reminds you to turn something on.

To check a real notification, ask another member to @mention you in a comment (pick your name from the suggestions; typing it is not a mention). It should arrive in your DevStride chat in Teams within a minute. Select Open mention in DevStride to jump to the item.

Managing the integration

To…Do this
See which Microsoft organization is connectedConfigure Settings → Integrations → Microsoft Teams → Connected Microsoft Tenant
Switch to another Microsoft organizationSelect Remove, sign out of Microsoft in this browser, then connect again
Update the app after DevStride releases a new versionDownload the package again from the Integrations page and upload it over the existing DevStride app under Teams apps → Manage apps in the Teams admin center.
Control who can use the appTeams admin center → Teams apps → Manage apps → DevStride
Install the app for more peopleInstall the app for people: choose them and select Install
Disconnect the organizationSelect Remove, then Remove Connection. Teams chats DevStride already knows are kept, so reconnecting later picks up where it left off. Other DevStride organizations keep their own connections.
Stop your own Teams messagesIn Notification Settings, untick Teams for mentions and clear the Teams tab. Or remove the DevStride app in Teams.

If something goes wrong

What you seeWhat to do
DevStride shows Microsoft Teams was not connected after MicrosoftThe page names the reason (the link was already used or over an hour old, the approval finished in another browser or the browser blocked DevStride's cookie, no administrator has approved DevStride, a personal account was used, or the approval was declined) and its link takes you back to the step that fixes it.
Microsoft asks for an administrator's approvalA Microsoft 365 administrator must approve DevStride for the organization. Manage Integrations in DevStride does not grant Microsoft approval.
Microsoft says the application is missing from your organization (AADSTS650052)Contact DevStride support with the error. Do not create an app or secret yourself.
DevStride is missing from Built for your org, or shows Request instead of AddCheck the package was uploaded to this organization's catalog and that the person is allowed to use it, then allow a few hours for Teams to update.
Something went wrong while adding the appCheck Apps → Manage your apps: it may have been added anyway. Otherwise refresh Teams and try again later.
The welcome message says DevStride could not find an account for your Microsoft sign-inSign in to Teams with the same email address as your DevStride account, or have that address invited to DevStride. Then remove the app and add it again.
The test says the app is not addedAdd the DevStride app in Teams, signed in with the same email address as your DevStride account. If it is already there, remove it and add it again.
The test says Teams refused the message, or your administrator blocked the appAsk your Teams administrator to allow DevStride for you, then remove and add the app and test again.
The test arrives but real notifications do notCheck that Teams is ticked for mentions or activities, that you can see the item, and that your Microsoft email matches your verified DevStride email. Then ask someone to create a new event; old notifications are not re-sent.
A message opens the wrong DevStride environmentThe package came from another environment. Download it again from the environment you use and upload it again.

When contacting support, include your DevStride organization, the Microsoft organization name, the person's email, the approximate time and time zone, the item number and any Microsoft error code. Never send passwords or secrets.