content: Launch post — Connect Microsoft Teams Without a Setup Call - #837
content: Launch post — Connect Microsoft Teams Without a Setup Call#837frances720 wants to merge 1 commit into
Conversation
Generated by launch-post skill.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
There was a problem hiding this comment.
Documentation review — self-serve Microsoft Teams connect launch post
Thanks for this, Frances. Nice tight post that follows the launch-article structure (problem → what it does now → who benefits), stays in the dry, second-person product-updates voice, and correctly wires up the frontmatter, CTAs, and the docs link. I reviewed it on both mandatory dimensions — correctness against source/product, and doc quality/style — plus audience fit and repo conventions.
What I verified
- Against the current product docs (source of truth): the exact button label "Link App & Grant Read Channels", the download-app-package step, the install-via-Teams-Admin-Center step, and the step order all match the current Microsoft Teams integration guide (Steps 1–4). Those claims are accurate against how the product reads today.
- Against the cited source PR: I researched Promptless/promptless#3641. Heads up that #3641 is only part of this feature — it shipped the OIDC "Enable" sign-in bind (merged 2026-06-17, no admin consent). The "Link App & Grant Read Channels" button and the admin-consent behavior your post/flow rely on actually came from later follow-up work (the 2026-06-19 admin-consent / Graph-channels change), not #3641. The post describes the current combined state correctly; it's the PR-body citation that's incomplete. Not a blocker for the prose, but worth citing the follow-up PR too if you want the source trail to hold up.
- Live dashboard grounding: I signed into the live Integrations page to ground the UI steps. The test org already has Teams connected, so the pre-connection flow (download package / "Link App & Grant Read Channels") wasn't reachable to screenshot without disconnecting a live integration, which I didn't do. One thing I could confirm live: the Teams card shows no "beta" badge (Google Drive's card does), which feeds into the beta point below.
Why COMMENT and not approve: three correctness/completeness items to reconcile before publish, plus one repo-convention fix. Details inline. None require me to rewrite the post — suggested wording is in the inline comments. The merge call is yours.
|
|
||
| ## 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. |
There was a problem hiding this comment.
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:
| 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. |
| 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. |
There was a problem hiding this comment.
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.
|
|
||
| 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. |
There was a problem hiding this comment.
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.
|
|
||
| 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. |
There was a problem hiding this comment.
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:
| 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. |
2 participants
Feature
Microsoft Teams now connects to Promptless without a setup call. Download the app package, install it in the Teams tenant, and link the tenant via the Integrations page.
Entries considered this run
Window: 2026-08-03 → 2026-08-10. Full triage table is in PR #836 (the companion post for this run). This PR covers the second qualifier.
Covered entry (full text)
Source: commit 1f8b498 (June 2026 changelog entry).
PR(s) researched
File
src/content/blog/product-updates/self-serve-teams-connect.mdxAI-generated draft — needs human review before publishing.
Generated by Claude Code