From 9529664e91d5625e2d2df3e3322927a97dc7a8b7 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Mon, 23 Feb 2026 16:27:28 -0800 Subject: [PATCH 1/9] Add docs for signin/failure handling --- .../{sso-setup.md => sso-setup.mdx} | 23 +++++++++++++++++++ .../user-authentication/csharp.incl.md | 11 +++++++++ .../user-authentication/python.incl.md | 14 +++++++++++ .../user-authentication/typescript.incl.md | 10 ++++++++ .../in-depth-guides/user-authentication.mdx | 10 ++++++++ 5 files changed, 68 insertions(+) rename teams.md/docs/main/teams/user-authentication/{sso-setup.md => sso-setup.mdx} (75%) diff --git a/teams.md/docs/main/teams/user-authentication/sso-setup.md b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx similarity index 75% rename from teams.md/docs/main/teams/user-authentication/sso-setup.md rename to teams.md/docs/main/teams/user-authentication/sso-setup.mdx index 9e40f804b5..38943dec0f 100644 --- a/teams.md/docs/main/teams/user-authentication/sso-setup.md +++ b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx @@ -3,6 +3,8 @@ sidebar_position: 1 summary: Describes how to configure SSO in Teams --- +import LangLink from '@site/src/components/LangLink'; + # SSO Setup This section describes how to configure the Azure Bot Service (ABS), the Entra App Registration and the Teams manifest to enable Single-Sign-On (SSO) for your Teams app. @@ -80,3 +82,24 @@ The Teams application manifest needs to be updated to reflect the settings confi } ``` +## Troubleshooting SSO + +### `signin/failure` with `resourcematchfailed` + +If you see a warning in your app logs like: + +> Sign-in failed for user "..." in conversation "...": resourcematchfailed -- Resource match failed + +This means Teams attempted the SSO token exchange but failed because the token exchange resource URI does not match your Entra app registration. To fix this: + +1. **Verify "Expose an API"** in your Entra app registration: the Application ID URI must be set (typically `api://`) +2. **Verify the `access_as_user` scope** is defined under "Expose an API" +3. **Verify pre-authorized client applications** include the Teams Desktop (`1fec8e78-bce4-4aaf-ab1b-5451cc387264`) and Teams Web (`5e3ce6c0-2b1f-4285-8d4b-75ee78787346`) client IDs +4. **Verify the Token Exchange URL** in your Azure Bot OAuth connection matches the Application ID URI exactly + +:::tip +If you don't need SSO and only want standard OAuth (sign-in button), leave the **Token Exchange URL** blank in your OAuth connection settings. +::: + +To handle `signin/failure` programmatically in your app, see Handling Sign-In Failures in the User Authentication guide. + diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md index 1222be1cf3..8b1976b5fe 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md @@ -88,6 +88,17 @@ teams.OnMessage("/signout", async context => await context.Send("you have been signed out!"); }); ``` + + +```cs +teams.OnFailure(async (context, cancellationToken) => +{ + var failure = context.Activity.Value; + Console.WriteLine($"Sign-in failed: {failure?.Code} - {failure?.Message}"); + await context.Send("Sign-in failed. Please contact your admin.", cancellationToken); +}); +``` + N/A \ No newline at end of file diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md index c1fecee3ae..e876dbf1f9 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md @@ -86,6 +86,20 @@ async def handle_signout_message(ctx: ActivityContext[MessageActivity]): await ctx.send("You have been signed out!") ``` + + +```python +@app.on_signin_failure() +async def handle_signin_failure(ctx): + failure = ctx.activity.value + print(f"Sign-in failed: {failure.code} - {failure.message}") + await ctx.send("Sign-in failed. Please contact your admin.") +``` + +:::note +In Python, registering a custom handler does **not** replace the built-in default handler. Both will run as part of the middleware chain. If you have a catch-all `@app.on_invoke()` handler, it must call `await ctx.next()` for the `signin/failure` handler to execute. +::: + import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md index 2df8cf15f8..d88edfea16 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md @@ -81,6 +81,16 @@ app.message('/signout', async ({ send, signout, isSignedIn }) => { }); ``` + + +```ts +app.on('signin.failure', async ({ activity, send }) => { + const { code, message } = activity.value; + console.log(`Sign-in failed: ${code} - ${message}`); + await send('Sign-in failed. Please contact your admin.'); +}); +``` + import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx b/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx index d1bb92a949..512e8d27a9 100644 --- a/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx +++ b/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx @@ -96,6 +96,16 @@ You can signout by calling the `signout` method, this will remove the token from +## Handling Sign-In Failures + +When using SSO, if the token exchange fails Teams sends a `signin/failure` invoke activity to your app. The SDK includes a built-in default handler that logs a warning with actionable troubleshooting guidance. You can optionally register your own handler to customize the behavior: + + + +:::tip +The most common failure code is `resourcematchfailed`, which means the Token Exchange URL in your OAuth connection does not match the Application ID URI in your Entra app registration's "Expose an API" configuration. See [SSO Setup - Troubleshooting](/teams/user-authentication/sso-setup#troubleshooting-sso) for details. +::: + ## Resources From 6de8158a454e40cacc351e081572d2e8f025c5b8 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Mon, 23 Feb 2026 16:34:29 -0800 Subject: [PATCH 2/9] Update PY note --- .../include/in-depth-guides/user-authentication/python.incl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md index e876dbf1f9..aee5432a42 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md @@ -97,7 +97,7 @@ async def handle_signin_failure(ctx): ``` :::note -In Python, registering a custom handler does **not** replace the built-in default handler. Both will run as part of the middleware chain. If you have a catch-all `@app.on_invoke()` handler, it must call `await ctx.next()` for the `signin/failure` handler to execute. +In Python, registering a custom handler does **not** replace the built-in default handler. Both will run as part of the middleware chain. ::: From b4ca3ac41ed65e00196b447b105d598a79f8f563 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Mon, 23 Feb 2026 17:19:58 -0800 Subject: [PATCH 3/9] Fix file reference --- teams.md/src/pages/templates/migrations/slack-bolt.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/teams.md/src/pages/templates/migrations/slack-bolt.mdx b/teams.md/src/pages/templates/migrations/slack-bolt.mdx index 959e4c726e..3b8c98a3a1 100644 --- a/teams.md/src/pages/templates/migrations/slack-bolt.mdx +++ b/teams.md/src/pages/templates/migrations/slack-bolt.mdx @@ -75,7 +75,7 @@ There are two primary types of user authentication for Teams and Slack: authenti In Slack, if you want to use Slack REST APIs that require user-delegated scopes, you need to implement an OAuth 2.0 installation flow in your application to obtain and store Slack user tokens, even if the app was already installed by another user. In Teams, you can leverage Teams SSO to obtain user Entra tokens for calling Graph REST APIs. The Teams SDK integrates with Teams SSO and Azure Bot Token Service to handle token acquisition, storage, and refresh automatically for you. -First, follow the instructions in the [Teams SSO guide](../../../../docs/main/teams/user-authentication/sso-setup.md). +First, follow the instructions in the [Teams SSO guide](../../../../docs/main/teams/user-authentication/sso-setup.mdx). Then, configure the authentication in your code. From f6467d53d52366f318d92f152c2ad766228c8fda Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Tue, 3 Mar 2026 09:01:56 -0800 Subject: [PATCH 4/9] Update C# docs --- .../include/in-depth-guides/user-authentication/csharp.incl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md index 8b1976b5fe..362312e00a 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md @@ -91,7 +91,7 @@ teams.OnMessage("/signout", async context => ```cs -teams.OnFailure(async (context, cancellationToken) => +teams.OnSigninFailure(async (context, cancellationToken) => { var failure = context.Activity.Value; Console.WriteLine($"Sign-in failed: {failure?.Code} - {failure?.Message}"); From 32772596752254340c1b5bb8f330327acd11ff05 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Wed, 4 Mar 2026 11:24:02 -0800 Subject: [PATCH 5/9] Update with complete list of failure codes --- .../teams/user-authentication/sso-setup.mdx | 22 ++++++++++++++++++- .../in-depth-guides/user-authentication.mdx | 2 +- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/teams.md/docs/main/teams/user-authentication/sso-setup.mdx b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx index 38943dec0f..a2207c7f75 100644 --- a/teams.md/docs/main/teams/user-authentication/sso-setup.mdx +++ b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx @@ -84,7 +84,27 @@ The Teams application manifest needs to be updated to reflect the settings confi ## Troubleshooting SSO -### `signin/failure` with `resourcematchfailed` +When SSO fails, Teams sends a `signin/failure` invoke activity to your bot with a `code` and `message` describing the error. The SDK's default handler logs a warning with these details. + +### Failure codes + +| Code | Silent | Description | +|------|--------|-------------| +| `installappfailed` | No | Failed to install the app in the user's personal scope (group chat SSO flow). | +| `authrequestfailed` | No | The SSO auth request failed after app installation. | +| `installedappnotfound` | Yes | The bot app is not installed for the user or group chat. *(most common)* | +| `invokeerror` | Yes | A generic error occurred during the SSO invoke flow. | +| `resourcematchfailed` | Yes | The token exchange resource URI on the OAuthCard does not match the Application ID URI in the Entra app registration's "Expose an API" section. *(common)* | +| `oauthcardnotvalid` | Yes | The bot's OAuthCard could not be parsed. | +| `tokenmissing` | Yes | AAD token acquisition failed. | + +"Silent" failures produce no user-facing feedback in the Teams client — the user sees nothing and sign-in simply doesn't complete. "Non-silent" failures occur during the group chat SSO flow where the user is shown an install/auth card. + +:::note +The `userconsentrequired` and `interactionrequired` codes are handled by the Teams client via the OAuth card fallback flow and do not typically reach the bot. +::: + +### `resourcematchfailed` If you see a warning in your app logs like: diff --git a/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx b/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx index 512e8d27a9..876abb8353 100644 --- a/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx +++ b/teams.md/src/pages/templates/in-depth-guides/user-authentication.mdx @@ -103,7 +103,7 @@ When using SSO, if the token exchange fails Teams sends a `signin/failure` invok :::tip -The most common failure code is `resourcematchfailed`, which means the Token Exchange URL in your OAuth connection does not match the Application ID URI in your Entra app registration's "Expose an API" configuration. See [SSO Setup - Troubleshooting](/teams/user-authentication/sso-setup#troubleshooting-sso) for details. +The most common failure codes are `installedappnotfound` (bot app not installed for the user) and `resourcematchfailed` (Token Exchange URL doesn't match the Application ID URI). See [SSO Setup - Troubleshooting](/teams/user-authentication/sso-setup#troubleshooting-sso) for a full list of failure codes and troubleshooting steps. ::: From 2238f493f402619031043575ec54afade06405d8 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Fri, 6 Mar 2026 15:45:57 -0800 Subject: [PATCH 6/9] Apply PR feedback --- .../teams/user-authentication/sso-setup.mdx | 43 +---------------- .../troubleshooting-sso.mdx | 48 +++++++++++++++++++ 2 files changed, 50 insertions(+), 41 deletions(-) create mode 100644 teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx diff --git a/teams.md/docs/main/teams/user-authentication/sso-setup.mdx b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx index a2207c7f75..d7872a8e57 100644 --- a/teams.md/docs/main/teams/user-authentication/sso-setup.mdx +++ b/teams.md/docs/main/teams/user-authentication/sso-setup.mdx @@ -3,8 +3,6 @@ sidebar_position: 1 summary: Describes how to configure SSO in Teams --- -import LangLink from '@site/src/components/LangLink'; - # SSO Setup This section describes how to configure the Azure Bot Service (ABS), the Entra App Registration and the Teams manifest to enable Single-Sign-On (SSO) for your Teams app. @@ -82,44 +80,7 @@ The Teams application manifest needs to be updated to reflect the settings confi } ``` -## Troubleshooting SSO - -When SSO fails, Teams sends a `signin/failure` invoke activity to your bot with a `code` and `message` describing the error. The SDK's default handler logs a warning with these details. - -### Failure codes - -| Code | Silent | Description | -|------|--------|-------------| -| `installappfailed` | No | Failed to install the app in the user's personal scope (group chat SSO flow). | -| `authrequestfailed` | No | The SSO auth request failed after app installation. | -| `installedappnotfound` | Yes | The bot app is not installed for the user or group chat. *(most common)* | -| `invokeerror` | Yes | A generic error occurred during the SSO invoke flow. | -| `resourcematchfailed` | Yes | The token exchange resource URI on the OAuthCard does not match the Application ID URI in the Entra app registration's "Expose an API" section. *(common)* | -| `oauthcardnotvalid` | Yes | The bot's OAuthCard could not be parsed. | -| `tokenmissing` | Yes | AAD token acquisition failed. | - -"Silent" failures produce no user-facing feedback in the Teams client — the user sees nothing and sign-in simply doesn't complete. "Non-silent" failures occur during the group chat SSO flow where the user is shown an install/auth card. - -:::note -The `userconsentrequired` and `interactionrequired` codes are handled by the Teams client via the OAuth card fallback flow and do not typically reach the bot. -::: - -### `resourcematchfailed` - -If you see a warning in your app logs like: - -> Sign-in failed for user "..." in conversation "...": resourcematchfailed -- Resource match failed - -This means Teams attempted the SSO token exchange but failed because the token exchange resource URI does not match your Entra app registration. To fix this: - -1. **Verify "Expose an API"** in your Entra app registration: the Application ID URI must be set (typically `api://`) -2. **Verify the `access_as_user` scope** is defined under "Expose an API" -3. **Verify pre-authorized client applications** include the Teams Desktop (`1fec8e78-bce4-4aaf-ab1b-5451cc387264`) and Teams Web (`5e3ce6c0-2b1f-4285-8d4b-75ee78787346`) client IDs -4. **Verify the Token Exchange URL** in your Azure Bot OAuth connection matches the Application ID URI exactly - -:::tip -If you don't need SSO and only want standard OAuth (sign-in button), leave the **Token Exchange URL** blank in your OAuth connection settings. -::: +## Troubleshooting -To handle `signin/failure` programmatically in your app, see Handling Sign-In Failures in the User Authentication guide. +If you encounter SSO errors, see the [Troubleshooting](troubleshooting-sso) guide for common issues and solutions. diff --git a/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx b/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx new file mode 100644 index 0000000000..2f02611556 --- /dev/null +++ b/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx @@ -0,0 +1,48 @@ +--- +sidebar_position: 2 +title: Troubleshooting +summary: Common SSO errors and how to resolve them +--- + +import LangLink from '@site/src/components/LangLink'; + +# SSO Troubleshooting + +When SSO fails, Teams sends a `signin/failure` invoke activity to your bot with a `code` and `message` describing the error. The SDK's default handler logs a warning with these details. + +## Failure codes + +| Code | Silent | Description | +|------|--------|-------------| +| `installappfailed` | No | Failed to install the app in the user's personal scope (group chat SSO flow). | +| `authrequestfailed` | No | The SSO auth request failed after app installation. | +| `installedappnotfound` | Yes | The bot app is not installed for the user or group chat. *(most common)* | +| `invokeerror` | Yes | A generic error occurred during the SSO invoke flow. | +| `resourcematchfailed` | Yes | The token exchange resource URI on the OAuthCard does not match the Application ID URI in the Entra app registration's "Expose an API" section. *(common)* | +| `oauthcardnotvalid` | Yes | The bot's OAuthCard could not be parsed. | +| `tokenmissing` | Yes | AAD token acquisition failed. | + +"Silent" failures produce no user-facing feedback in the Teams client — the user sees nothing and sign-in simply doesn't complete. "Non-silent" failures occur during the group chat SSO flow where the user is shown an install/auth card. + +:::note +The `userconsentrequired` and `interactionrequired` codes are handled by the Teams client via the OAuth card fallback flow and do not typically reach the bot. +::: + +## `resourcematchfailed` + +If you see a warning in your app logs like: + +> Sign-in failed for user "..." in conversation "...": resourcematchfailed -- Resource match failed + +This means Teams attempted the SSO token exchange but failed because the token exchange resource URI does not match your Entra app registration. To fix this: + +1. **Verify "Expose an API"** in your Entra app registration: the Application ID URI must be set (typically `api://`) +2. **Verify the `access_as_user` scope** is defined under "Expose an API" +3. **Verify pre-authorized client applications** include the Teams Desktop (`1fec8e78-bce4-4aaf-ab1b-5451cc387264`) and Teams Web (`5e3ce6c0-2b1f-4285-8d4b-75ee78787346`) client IDs +4. **Verify the Token Exchange URL** in your Azure Bot OAuth connection matches the Application ID URI exactly + +:::tip +If you don't need SSO and only want standard OAuth (sign-in button), leave the **Token Exchange URL** blank in your OAuth connection settings. +::: + +To handle `signin/failure` programmatically in your app, see Handling Sign-In Failures in the User Authentication guide. From a46236fb59c120d40fe4fe154b1442f7b40c53a7 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Fri, 6 Mar 2026 15:47:14 -0800 Subject: [PATCH 7/9] Add manifest verification line --- .../docs/main/teams/user-authentication/troubleshooting-sso.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx b/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx index 2f02611556..920898e707 100644 --- a/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx +++ b/teams.md/docs/main/teams/user-authentication/troubleshooting-sso.mdx @@ -40,6 +40,7 @@ This means Teams attempted the SSO token exchange but failed because the token e 2. **Verify the `access_as_user` scope** is defined under "Expose an API" 3. **Verify pre-authorized client applications** include the Teams Desktop (`1fec8e78-bce4-4aaf-ab1b-5451cc387264`) and Teams Web (`5e3ce6c0-2b1f-4285-8d4b-75ee78787346`) client IDs 4. **Verify the Token Exchange URL** in your Azure Bot OAuth connection matches the Application ID URI exactly +5. **Verify the `webApplicationInfo.resource`** in your Teams app manifest matches the Application ID URI :::tip If you don't need SSO and only want standard OAuth (sign-in button), leave the **Token Exchange URL** blank in your OAuth connection settings. From 1ad82ac602646b12d5cc271cdabff9b9f37d8049 Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Fri, 6 Mar 2026 16:44:45 -0800 Subject: [PATCH 8/9] Remove 'Please contact your admin' line --- .../include/in-depth-guides/user-authentication/csharp.incl.md | 2 +- .../include/in-depth-guides/user-authentication/python.incl.md | 2 +- .../in-depth-guides/user-authentication/typescript.incl.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md index 362312e00a..216d0a304c 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md @@ -95,7 +95,7 @@ teams.OnSigninFailure(async (context, cancellationToken) => { var failure = context.Activity.Value; Console.WriteLine($"Sign-in failed: {failure?.Code} - {failure?.Message}"); - await context.Send("Sign-in failed. Please contact your admin.", cancellationToken); + await context.Send("Sign-in failed.", cancellationToken); }); ``` diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md index aee5432a42..d1c51f6e3e 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/python.incl.md @@ -93,7 +93,7 @@ async def handle_signout_message(ctx: ActivityContext[MessageActivity]): async def handle_signin_failure(ctx): failure = ctx.activity.value print(f"Sign-in failed: {failure.code} - {failure.message}") - await ctx.send("Sign-in failed. Please contact your admin.") + await ctx.send("Sign-in failed.") ``` :::note diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md index d88edfea16..b26b8a40e9 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/typescript.incl.md @@ -87,7 +87,7 @@ app.message('/signout', async ({ send, signout, isSignedIn }) => { app.on('signin.failure', async ({ activity, send }) => { const { code, message } = activity.value; console.log(`Sign-in failed: ${code} - ${message}`); - await send('Sign-in failed. Please contact your admin.'); + await send('Sign-in failed.'); }); ``` From a5f34d22ab8e835ec5c36ef81812b58c954a569e Mon Sep 17 00:00:00 2001 From: Corina Gum <> Date: Mon, 9 Mar 2026 11:10:11 -0700 Subject: [PATCH 9/9] Fix capitalization issue for C# --- .../include/in-depth-guides/user-authentication/csharp.incl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md index 216d0a304c..05e62f5b75 100644 --- a/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md +++ b/teams.md/src/components/include/in-depth-guides/user-authentication/csharp.incl.md @@ -91,7 +91,7 @@ teams.OnMessage("/signout", async context => ```cs -teams.OnSigninFailure(async (context, cancellationToken) => +teams.OnSignInFailure(async (context, cancellationToken) => { var failure = context.Activity.Value; Console.WriteLine($"Sign-in failed: {failure?.Code} - {failure?.Message}");