@@ -43,7 +43,7 @@ When you run `atk provision --env dev`, the following Azure resources are create
4343| ** User Assigned Managed Identity** | Bot identity (no passwords!) | ` {resourceBaseName}-identity ` |
4444| ** App Service Plan** | Compute resources (Linux) | ` {resourceBaseName}-plan ` |
4545| ** Web App** | Hosts .NET 9 bot application | ` {resourceBaseName}-app ` |
46- | ** Azure Bot Service** | Bot Framework registration | ` {resourceBaseName} ` |
46+ | ** Azure Bot Service** | Azure Bot Service registration | ` {resourceBaseName} ` |
4747| ** Entra ID App Registration** | SSO authentication | ` {botDisplayName} ` |
4848| ** OAuth Connection** | SSO token exchange | ` SsoConnection ` |
4949
@@ -151,35 +151,20 @@ Edit `M365Agent/env/.env.dev`:
151151
152152``` bash
153153# ============================================================================
154- # Azure Configuration (REQUIRED - Set these before provisioning)
154+ # Microsoft Foundry Configuration (REQUIRED - Set these before provisioning)
155155# ============================================================================
156- AZURE_SUBSCRIPTION_ID=< your-subscription-id>
157- AZURE_RESOURCE_GROUP_NAME=rg-m365agent-prod
158- RESOURCE_SUFFIX=prod123
156+ AZURE_AI_FOUNDRY_PROJECT_ENDPOINT=< URL of your MS Foundry endpoint>
157+ AGENT_ID=< Agent ID that start by asst_>
159158
160- # ============================================================================
161- # Environment Settings
162- # ============================================================================
163- TEAMSFX_ENV=dev
164- APP_NAME_SUFFIX=dev
165-
166- # ============================================================================
167- # Output Variables (Auto-populated by atk provision)
168- # ============================================================================
169- # Do not edit these - they are populated automatically during deployment
170159```
171160
172- ** Tips:**
173- - Get your subscription ID: ` az account show --query id -o tsv `
174- - ` RESOURCE_SUFFIX ` must be globally unique (lowercase, alphanumeric, max 10 chars)
175- - Use descriptive names like ` prod001 ` , ` dev001 ` , etc.
176-
177161### Step 2: Provision Azure Infrastructure
178162
179- ``` powershell
180- cd M365Agent
181- atk provision --env dev
182- ```
163+ ** Using Microsoft 365 Agents Toolkit UI (Recommended):**
164+ 1 . Open the ** Microsoft 365 Agents Toolkit** extension panel in VS Code or Visual Studio
165+ 2 . Navigate to the ** Lifecycle** section
166+ 3 . Select environment: ** dev**
167+ 4 . Click ** Provision** to create Azure resources
183168
184169** What happens:**
1851701 . ✅ Creates Teams app registration in Teams Developer Portal
@@ -193,9 +178,9 @@ atk provision --env dev
193178```
194179✓ Teams app created successfully
195180✓ Provisioning Azure resources...
196- ✓ Managed Identity created: botprod123 -identity
197- ✓ App Service deployed: https://botprod123 -app.azurewebsites.net
198- ✓ Bot Service registered: botprod123
181+ ✓ Managed Identity created: <AppName> -identity
182+ ✓ App Service deployed: https://<AppName> -app.azurewebsites.net
183+ ✓ Bot Service registered: <AppName>
199184✓ SSO App Registration created
200185✓ OAuth Connection configured
201186✓ Teams app package validated
@@ -204,12 +189,20 @@ atk provision --env dev
204189
205190** Duration:** ~ 5-8 minutes
206191
207- ### Step 3: Deploy Application Code
208-
192+ ** Alternatively, using CLI:**
209193``` powershell
210- atk deploy --env dev
194+ cd M365Agent
195+ atk provision --env dev
211196```
212197
198+ ### Step 3: Deploy Application Code
199+
200+ ** Using Microsoft 365 Agents Toolkit UI (Recommended):**
201+ 1 . In the ** Microsoft 365 Agents Toolkit** extension panel
202+ 2 . Navigate to the ** Lifecycle** section
203+ 3 . Select environment: ** dev**
204+ 4 . Click ** Deploy** to publish application code
205+
213206** What happens:**
2142071 . ✅ Builds .NET application (` dotnet publish -c Release ` )
2152082 . ✅ Creates deployment package
@@ -226,7 +219,15 @@ atk deploy --env dev
226219
227220** Duration:** ~ 2-3 minutes
228221
229- ### Step 4: Install in Teams
222+ ** Alternatively, using CLI:**
223+ ``` powershell
224+ cd M365Agent
225+ atk deploy --env dev
226+ ```
227+
228+ ### Step 4: Install in Microsoft 365 Copilot & Microsoft Teams
229+
230+ ** Note:** The app is automatically registered in Teams Developer Portal during provisioning. However, you can manually install it if needed:
230231
2312321 . Open ** Microsoft Teams**
2322332 . Go to ** Apps** → ** Manage your apps**
@@ -261,7 +262,7 @@ Location: Same as resource group
261262- ✅ No secrets to manage or rotate
262263- ✅ Secure authentication to Azure services
263264- ✅ Integrated Azure RBAC support
264- - ✅ Used as bot's identity in Bot Framework
265+ - ✅ Used as bot's identity in Azure Bot Service
265266
266267---
267268
@@ -315,7 +316,7 @@ Location: Same as resource group
315316
316317** Module:** ` modules/azurebot.bicep `
317318
318- ** Purpose:** Registers your web service as a bot with the Bot Framework and enables Teams channel.
319+ ** Purpose:** Registers your web service as a bot with Azure Bot Service and enables Teams channel.
319320
320321** Resources Created:**
321322
@@ -885,7 +886,7 @@ You've successfully deployed your M365 Agent to Azure! 🎉
885886- [Microsoft 365 Agents Toolkit Documentation](https://aka.ms/teams-toolkit-docs)
886887- [Azure Bot Service Documentation](https://learn.microsoft.com/azure/bot-service/)
887888- [Bicep Documentation](https://learn.microsoft.com/azure/azure-resource-manager/bicep/)
888- - [Bot Framework SDK](https://github.com/microsoft/botbuilder-dotnet )
889+ - [M365 Agent SDK](https://github.com/microsoft/agents )
889890
890891**Support:**
891892- GitHub Issues: [Teams Toolkit Repository](https://github.com/OfficeDev/TeamsFx/issues)
0 commit comments