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.
| Step | Who | How long |
|---|---|---|
| 1. Connect your Microsoft organization | A DevStride member with Manage Integrations, after a Microsoft 365 administrator approves DevStride once | A few minutes |
| 2. Make the app available in Teams | Your Teams administrator | A few minutes, then up to a few hours for Teams to show it |
| 3. Add the app | Each person who wants Teams notifications, or an administrator for chosen people | One minute |
| 4. Choose notifications | Each person, in DevStride | One minute |
| 5. Send yourself a test | Each person, in DevStride | One minute |
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.
Do this once per DevStride organization.
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.
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.
devstride-teams-1.0.7.zip). Keep it zipped: you upload the ZIP itself. It holds a manifest and icons, no secrets.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.
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.
Each person gets a result:
| Result | What it means |
|---|---|
| Installed | The app is in their Teams. Teams tells DevStride where to send their messages once it appears, which can take a minute. |
| Already installed | Nothing to do. |
| Not found | Their 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 person | Usually 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 approved | The Microsoft administrator approval is missing or was removed. |
| Not an active member with a verified email | Nothing was attempted. |
| Not attempted / Microsoft asked to wait | Install 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.
If an administrator installed it for you, it is already in your Teams: skip to step 3 below.
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:
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.
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.
In Notification Settings, the Your Microsoft Teams notifications panel checks your setup:
| Row | What it tells you |
|---|---|
| Connected | Your organization is connected to Microsoft Teams, and to which Microsoft organization. |
| App added | You 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. |
| Shown only when your DevStride email is not verified yet. Nothing is sent until it is. | |
| Test | Select Send me a test message. The panel says whether Microsoft accepted it, or exactly what is missing. |
| Received | After 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.
| To… | Do this |
|---|---|
| See which Microsoft organization is connected | Configure Settings → Integrations → Microsoft Teams → Connected Microsoft Tenant |
| Switch to another Microsoft organization | Select Remove, sign out of Microsoft in this browser, then connect again |
| Update the app after DevStride releases a new version | Download 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 app | Teams admin center → Teams apps → Manage apps → DevStride |
| Install the app for more people | Install the app for people: choose them and select Install |
| Disconnect the organization | Select 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 messages | In Notification Settings, untick Teams for mentions and clear the Teams tab. Or remove the DevStride app in Teams. |
| What you see | What to do |
|---|---|
| DevStride shows Microsoft Teams was not connected after Microsoft | The 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 approval | A 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 Add | Check 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 app | Check 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-in | Sign 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 added | Add 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 app | Ask your Teams administrator to allow DevStride for you, then remove and add the app and test again. |
| The test arrives but real notifications do not | Check 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 environment | The 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.