Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
38 changes: 33 additions & 5 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 4 additions & 1 deletion teams.md/LANGUAGE-INCLUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@ Shared content for all languages.
The package name is <LanguageInclude section="package-name" />. <!-- Inline: from include files -->

<!-- NEW: Inline content without separate include files -->

The context type is <LanguageInclude content={{"typescript": "`IContext`", "python": "`Context`"}} />.
```

Expand Down Expand Up @@ -103,15 +104,17 @@ N/A
For simple, short language-specific text (like API names, method names, or simple phrases), you can use inline content directly in templates without creating separate include files:

```mdx
<LanguageInclude content={{"typescript": "`send`", "csharp": "`SendAsync`", "python": "`send`"}} />
<LanguageInclude content={{ typescript: '`send`', csharp: '`SendAsync`', python: '`send`' }} />
```

**When to use inline content:**

- Short text snippets (API names, method names, parameter names)
- Simple differences between languages
- Content that's easier to read inline than in separate files

**When to use include files:**

- Code examples
- Complex or multi-line content
- Content that benefits from syntax highlighting
Expand Down
2 changes: 1 addition & 1 deletion teams.md/docs/main/privacy.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@ llms: ignore

# Privacy Policy

We partner with Microsoft Clarity to capture how you use and interact with our website through behavioral metrics, heatmaps, and session replay to improve and market our products/services. Website usage data is captured using first and third-party cookies and other tracking technologies to determine the popularity of products/services and online activity. Additionally, we use this information for site optimization and fraud/security purposes. For more information about how Microsoft collects and uses your data, visit the [Microsoft Privacy Statement](https://www.microsoft.com/en-us/privacy/privacystatement).
We partner with Microsoft Clarity to capture how you use and interact with our website through behavioral metrics, heatmaps, and session replay to improve and market our products/services. Website usage data is captured using first and third-party cookies and other tracking technologies to determine the popularity of products/services and online activity. Additionally, we use this information for site optimization and fraud/security purposes. For more information about how Microsoft collects and uses your data, visit the [Microsoft Privacy Statement](https://www.microsoft.com/en-us/privacy/privacystatement).
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ Client Secret authentication is the simplest method, using a password-like secre
## Prerequisites

Before you begin, ensure you have:

- An Azure subscription
- Permissions to create App Registrations and Azure Bot Services

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ Federated Identity Credentials (FIC) allows you to assign managed identities dir
## Prerequisites

Before you begin, ensure you have:

- An Azure subscription
- Permissions to create App Registrations, Azure Bot Services, and manage identities
- A compute resource where your bot will be hosted (App Service, Container App, VM, etc.)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ This error occurs when the application has a single-tenant Azure Bot Service (`m

3. **Search for your application**
Use the **BOT_ID** from your environment file:

- Local development → `env/.env.local`
- Azure deployment → `env/.env.dev`

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ User Managed Identity authentication eliminates the need for secrets or password
## Prerequisites

Before you begin, ensure you have:

- An Azure subscription
- Permissions to create App Registrations, Azure Bot Services, and manage identities
- A compute resource where your bot will be hosted (App Service, Container App, VM, etc.)
Expand Down
2 changes: 1 addition & 1 deletion teams.md/docs/main/teams/core-concepts.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,4 +115,4 @@ Sideloading needs to be enabled in your tenant. If this is not the case, then yo

## Provisioning and Deployment

To test your app in Teams, you will at minimum need to have a provisioned Azure bot. You are likely to have other provisionied resources such as storage. Please see the Microsoft Learn [Provision cloud resources](https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/provision) documentation for provisioning and deployment using Visual Studio Code and to a container service.
To test your app in Teams, you will at minimum need to have a provisioned Azure bot. You are likely to have other provisionied resources such as storage. Please see the Microsoft Learn [Provision cloud resources](https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/provision) documentation for provisioning and deployment using Visual Studio Code and to a container service.
6 changes: 1 addition & 5 deletions teams.md/docs/main/teams/enabling-in-copilot.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,11 +68,7 @@ Here's how the `copilotAgents` section fits into the overall manifest structure:
"bots": [
{
"botId": "${{BOT_ID}}",
"scopes": [
"personal",
"team",
"groupchat"
],
"scopes": ["personal", "team", "groupchat"],
"supportsFiles": false,
"isNotificationOnly": false
}
Expand Down
4 changes: 2 additions & 2 deletions teams.md/docs/main/teams/user-authentication/_category_.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"label": "User Authentication Configuration",
"collapsed": true,
"position": 4,
"collapsed": true,
"position": 4
}
6 changes: 2 additions & 4 deletions teams.md/docs/main/teams/user-authentication/sso-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ You need an Entra ID App Registration to configure the OAuth Connection in Azure

![Entra client secret](/screenshots/entra-client-secret.png)

4. Configure the API. From `Expose an API`, Click `Add` to Application ID URI and accept the default value that will look like `api://<Your-Application-Id>`. Add the scope `access_as_user` and select who can _consent_.
4. Configure the API. From `Expose an API`, Click `Add` to Application ID URI and accept the default value that will look like `api://<Your-Application-Id>`. Add the scope `access_as_user` and select who can _consent_.

![Entra oauth scopes](/screenshots/entra-oauth-scopes.png)

Expand Down Expand Up @@ -64,10 +64,9 @@ az bot authsetting create \
--parameters "clientId=$appId" "clientSecret=$clientSecret" "tenantId=$tenantId" "tokenExchangeUrl=api://$appId"
```


## Configure the App Manifest

The Teams application manifest needs to be updated to reflect the settings configure above, with the `Application Id` and `Application ID URI`, if not using `devtunnels`, replace the valid domain with the domain hosting your application.
The Teams application manifest needs to be updated to reflect the settings configure above, with the `Application Id` and `Application ID URI`, if not using `devtunnels`, replace the valid domain with the domain hosting your application.

```json
"validDomains": [
Expand All @@ -79,4 +78,3 @@ The Teams application manifest needs to be updated to reflect the settings confi
"resource": "api://<Your-Application-Id>"
}
```

Loading