Skip to content

content: Launch post — Connect Microsoft Teams Without a Setup Call #837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
frances720 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

content: Launch post — Connect Microsoft Teams Without a Setup Call #837

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions src/content/blog/product-updates/self-serve-teams-connect.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
title: 'Connect Microsoft Teams to Promptless Without a Setup Call'
subtitle: Published August 2026
description: >-
Microsoft Teams now connects to Promptless without scheduling a setup call.
Download the app package, install it in your tenant, and link it on the
Integrations page.
date: '2026-08-10T00:00:00.000Z'
author: Frances
tag: Product Updates
section: Featured
hidden: false
---
import BlogNewsletterCTA from '@components/site/BlogNewsletterCTA.astro';
import BlogRequestDemo from '@components/site/BlogRequestDemo.astro';

You can now connect Microsoft Teams to Promptless without scheduling a setup call. The process is self-serve: download the Promptless Teams app package, install it into your Teams tenant, then link your tenant to your Promptless account on the Integrations page.

@promptless promptless Bot Aug 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness — "self-serve" is presented as unconditional, but the product has a fallback. The linked integration guide documents that the connect button reads "Contact Promptless" (not "Link App & Grant Read Channels") when Microsoft OAuth isn't configured for the org, in which case the user has to email help@gopromptless.ai to finish connecting. I confirmed this against the source: the connect flow is gated on an isMsTeamsOAuthConfigured() check, with a "Microsoft sign-in isn't configured… Contact Promptless support" fallback.

For a prospect reading a launch post this is usually fine to gloss, but since the whole headline is "without a setup call," consider a one-line hedge so a reader who hits the fallback isn't surprised — e.g. append to this paragraph: "If Microsoft sign-in isn't yet enabled for your organization, the Integrations page shows a Contact Promptless option instead." Your call whether that belongs in a launch post vs. staying in the reference guide.


## The problem

Teams integration used to require a call with the Promptless team. That made sense as a starting point, but it created a bottleneck for teams evaluating Promptless or wanting to add Teams during an active deployment. If you were running a pilot and decided mid-evaluation that you wanted to test Teams-triggered documentation updates, you had to stop and schedule time.

It also meant that adding Teams to an existing Promptless setup was not something you could do independently. Any admin who wanted to connect the integration had to wait on Promptless availability.

## What it does now

The Microsoft Teams integration now has a self-serve setup flow on the [Integrations page](https://app.gopromptless.ai/integrations).

Setup has three steps:

1. Download the Promptless app package from the Integrations page.
2. Install it into your Teams tenant via the Teams Admin Center.
3. Return to Promptless and click **Link App & Grant Read Channels** to bind your tenant to your Promptless organization.

@promptless promptless Bot Aug 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completeness / audience fit — the link step needs a Microsoft admin, which the step list omits. The integration guide's Step 4 says clicking Link App & Grant Read Channels "starts a Microsoft admin-consent sign-in that only a Microsoft admin can approve. If you're not an admin, ask your Microsoft admin to complete this step." Your post's audience is explicitly "Teams admins," but a Promptless admin isn't necessarily a Microsoft tenant admin, and this step gates on the latter.

Suggested tweak to step 3 so a non-admin reader knows what they'll hit:

Suggested change
3. Return to Promptless and click **Link App & Grant Read Channels** to bind your tenant to your Promptless organization.
3. Return to Promptless and click **Link App & Grant Read Channels** to bind your tenant to your Promptless organization. This step needs a Microsoft admin to approve the sign-in, so if you are not one, hand it to your Microsoft admin.


Once linked, Promptless can receive messages from Teams channels and personal chats where it's been installed, and it uses your Teams conversations as context for documentation suggestions.

<BlogNewsletterCTA />

## Who benefits most

Teams admins evaluating Promptless who want to test the full integration stack without going through a scheduling step. Also useful for existing Promptless customers who are adding Teams to their current setup — the full flow is in the docs and takes roughly as long as any other integration.

@promptless promptless Bot Aug 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Repo convention — banned em dash. The launch-article guide (.claude/skills/launch-post/references/launch-article-guide.md, banned-patterns list) bans em dashes in these posts: "Em dashes (—). Use a period or comma." This is the only one in the post.

Suggested fix — split into two sentences:

Suggested change
Teams admins evaluating Promptless who want to test the full integration stack without going through a scheduling step. Also useful for existing Promptless customers who are adding Teams to their current setup — the full flow is in the docs and takes roughly as long as any other integration.
Teams admins evaluating Promptless who want to test the full integration stack without going through a scheduling step. Also useful for existing Promptless customers who are adding Teams to their current setup. The full flow is in the docs and takes roughly as long as any other integration.


If you previously went through the manual connect process, your configuration is unchanged. This only affects new connections.

See the [Microsoft Teams integration guide](/docs/reference/integrations/microsoft-teams) for the complete setup steps.

@promptless promptless Bot Aug 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness — the page you link to still says the integration is in beta and asks users to contact Promptless to enable it, which contradicts this post's premise. The Microsoft Teams integration guide is titled "Microsoft Teams integration (beta)" and opens with a note: "The Microsoft Teams integration is in beta. Contact help@gopromptless.ai for more information about enabling this feature for your organization." A reader who clicks through from "connect it yourself, no setup call" lands on "it's beta, contact us to enable it."

One of the two is stale. I checked the live dashboard and the Teams integration card shows no beta badge (Google Drive's card does), which suggests the doc is the stale one. That doc fix is out of scope for this PR, but the contradiction is real — worth flagging to whoever owns the reference page (or noting in this PR) so the two get reconciled before this post drives traffic to a "(beta) / contact us" page. If Teams is still gated/beta for some orgs, this post's framing may be getting ahead of the rollout.


<BlogRequestDemo />
Loading