DevStride sends mentions and selected item updates to your personal chat with the DevStride app in Microsoft Teams. Setup requires both an organization connection and a personal app installation. Follow the steps below in order, starting with one recipient before rolling out to more people.
| Step | Who does it | How you know it is complete |
|---|---|---|
| 1. Connect the Microsoft tenant | A DevStride member with Manage Integrations, with access approved by a Microsoft administrator | DevStride shows Microsoft Teams is connected and the correct tenant name |
| 2. Make the app available | Your Microsoft Teams administrator | DevStride appears under Apps → Built for your org in Teams |
| 3. Add the personal app | Each person receiving notifications | DevStride is installed and its personal chat opens |
| 4. Choose notifications | Each recipient, in DevStride | Teams is selected for direct mentions and/or the desired activity rules |
| 5. Test delivery | A recipient and a second DevStride member | A new mention arrives in Teams and its link opens the correct item |
You can use your existing company Microsoft tenant and licensed Teams account. A separate test tenant or purchased domain is not required for ordinary setup. Connecting Teams does not change how you sign in to DevStride; Microsoft SSO is a separate integration.
After you connect the tenant, download the app package from DevStride itself:
The download is built for the environment you downloaded it from, so the app always sends notifications from that environment. A package from production (app.devstride.com) installs as DevStride; each other environment builds its own. You need Manage Integrations to download it. If the environment is not set up for Teams, the page says so instead of downloading.
Keep the downloaded file as a ZIP. Upload the ZIP itself; do not extract it. It contains the app manifest and icons, with no passwords or app secrets.
Your administrator uploads the package to your organization's catalog; you do not need to find a public Microsoft Teams Store listing. Customers using this integration do not need to create an Azure bot, register an Entra application, or generate a client secret.
Do this once for each DevStride organization, before installing the personal app.
Sign in to the intended DevStride environment, select the organization you want to connect, and open Configure Settings → Integrations → Microsoft Teams. Until a Microsoft organization is connected, the page walks you through three steps:
Back in DevStride, confirm Microsoft Teams is connected. The page shows the Microsoft tenant ID and the DevStride environment the connection belongs to — the app package you download from this page only works with that environment. If it is not the organization you expected, remove the connection, sign out of Microsoft in this browser (or use a private window), and connect again with the right work account.
A successful connection confirms that the connecting account has the required approval. It does not establish that consent was granted to every account in the Microsoft tenant. The connected page also lists what DevStride cannot check from here — your Teams admin settings, app availability and licenses for each person, and whether a message was read — so you know what to verify in the Teams admin center.
Your Microsoft Teams administrator completes this step. The catalog makes the app discoverable; each recipient still needs it installed for personal use.
The following path is available to administrators in Teams web or desktop:
Alternatively, use the Teams admin center: open Teams apps → Manage apps, then Upload new app (or Actions → Upload new app, depending on the interface), and upload the ZIP. Then open DevStride on the Manage apps page to choose who can use it, or use Edit installs to install it for everyone. Microsoft notes that catalog availability can take a few hours. See Microsoft's custom app administration guide.
Teams presents different upload choices based on your role and policies:
| Choice shown | When to use it |
|---|---|
| Upload an app to your org's app catalog | Administrator distribution to your organization; this is the setup path above |
| Upload a custom app | Personal or small-pilot installation, if your administrator permits it |
| Submit an app to your org | Request administrator review; submitting does not install or approve the app |
If you cannot upload, give the ZIP to your Teams administrator. Users who only need notifications can install the approved catalog app without permission to upload custom apps. Administrators can also use Microsoft's app deployment/setup controls to install it for selected users; verify the personal installation with a pilot recipient before a wider rollout.
Every person who wants Teams notifications completes this step, including the administrator who uploaded the package.
Adding the personal app registers your Teams account for delivery. Merely finding it in the catalog or opening an already-installed app does not repeat that registration. DevStride starts sending you Teams notifications from the moment you add the app. Anything that happened before then is not sent to Teams later, though it still reaches your other channels. If it was added before the tenant connection or during a setup failure, see troubleshooting before testing again.
Each recipient chooses their own preferences in the connected DevStride organization.
The direct-mention checkbox and the Teams activity grid are independent. Selecting one does not select the other. You can continue using Email, Slack, and the DevStride Notification Center alongside Teams.
If the Teams options do not appear, check the selected organization and reload the page after its Teams connection is complete. These controls confirm an organization connection, not a personal app installation. See notification settings for more examples.
Use this check before inviting more users to set up the integration. There is no separate Teams test-message button.
app.devstride.com. A development test should use DevStride Dev and open app.devstride.dev.Setup is complete when the recipient sees the real message and its link opens the correct item. A catalog entry, an empty bot chat, or the connected label alone is not a delivery test.
To test activity notifications as well, have another member make an assignment or other change covered by the recipient's Teams activity/role selections. To check opt-out behavior, turn off Teams direct mentions, create a new mention from the other account, and verify that it produces no Teams message; restore the preferred setting afterwards.
Always create a new event after installation, preference changes, or troubleshooting. Earlier notifications are not a substitute for a fresh test. In a development or sandbox environment, have DevStride support confirm outbound Teams delivery is enabled.
| What you see | Next step |
|---|---|
| After approving, DevStride shows Microsoft Teams was not connected | The page says which problem happened and what to do next: the approval link was already used or is more than an hour old; DevStride could not match the approval to the browser that started it (it finished in a different browser, or this browser blocked or cleared DevStride's cookie); no Microsoft administrator has approved DevStride yet; a personal Microsoft account was used; or the approval was declined. Select Back to Integrations — it reopens the setup step that fixes the problem. Each approval link works once, only in the browser that started it, and expires after one hour. |
| Microsoft asks for administrator approval | Have a Microsoft administrator approve the connection for the account being used. Manage Integrations in DevStride and an Azure subscription role do not grant Microsoft consent authority. |
Microsoft reports that the application/resource is missing from your tenant, including AADSTS650052 | Contact DevStride support and your Microsoft administrator with the error details. Support may need to help provision the existing DevStride authorization application in your tenant before approval can complete. Do not create a replacement app or secret. |
| Teams says you do not have permission to access the organization | Check the signed-in account and Microsoft tenant, then ask your Microsoft administrator to verify that the account has Teams access and the required license. |
| Upload is missing, or you only see Submit an app to your org | Ask your Teams administrator to upload the ZIP to the organization's catalog and allow the app for your account. Submission awaits approval. |
| DevStride is missing from Built for your org, or you see Request instead of Add | Check the tenant, catalog upload, and app availability for your user. Allow catalog/policy changes time to propagate. Your administrator can inspect the app in Teams admin center. |
| Teams shows Something went wrong during Add | Check Manage your apps first to see whether installation completed. If absent, refresh Teams and retry after catalog/policy changes have propagated. If the admin center reports app-management changes in progress, wait for that process; persistent errors need your Teams administrator or Microsoft support. |
| The chat is empty or says You cannot send messages to this bot | This is normal for a newly installed notification-only app. Use the second-member mention test above. |
| The Teams checkbox/tab is missing in DevStride | Check the selected DevStride organization and its connected Microsoft tenant, then reload Notification Settings. |
| Connected and installed, but no message | Confirm the Teams account's email matches the verified DevStride email, the DevStride membership is active, the recipient can access the item, and the sender selected a real @mention. |
| Only some events arrive | Check direct mentions separately from Teams conditional activity and role rules. Use a different member to create a fresh event. |
| The app was added before the organization was connected, or during a configuration failure | Ask DevStride support to check personal registration. After the connection/configuration is repaired, support may ask you to remove and add the personal app again. Reopening it alone does not repeat registration. |
| A development or sandbox environment is silent | Check that the app was downloaded from that environment's Integrations page, then confirm its outbound sending configuration with DevStride support. |
| The app is blocked or was removed | Have your Teams administrator allow it, then reinstall it for your account and run a new test. |
| A message opens the wrong environment | The app package came from a different DevStride environment. Download it again from the Integrations page of the environment you use, and upload that one. |
For support, include the DevStride environment and organization, Microsoft tenant name, recipient email, approximate test time and time zone, item number, expected notification, and any Microsoft error/correlation ID. Send these through your support channel; do not send passwords or app secrets.
To stop Teams delivery for the selected DevStride organization, open Configure Settings → Integrations → Microsoft Teams, select Remove, and confirm Remove Connection. Other DevStride organizations have their own connections.
To stop your own Teams notifications, turn off Teams direct mentions and clear the applicable Teams activity rules in My Account → Notification Settings. Removing the personal app in Teams also stops delivery to that installation; it does not remove other users' personal installations.