Merge pull request #301102 from vac0224/vc-tpe-aibot-steps-2025-06-12

Added app registration steps

Author: denrea

articles/communication-services/quickstarts/tpe/media/teams-phone-extensibility-app-registration-resources.png

@@ -33,17 +33,18 @@ This article describes how to grant consent to a server to receive calls directe
 The Azure Communication Services Resource Owner needs to run the following API operations. The resource owner need to provide consent for authorizing calls to the Azure Communication Services Resource from the Teams Resource Account. You can call the API using any REST tool or programmatically. The API supports GET, PUT, PATCH, and DELETE operations.  
 
 
-1. {YOUR-ACS-RESOURCE-ENDPOINT} in the request URI (RURI) path is the Azure Communication Services Resource fully qualified domain name (FQDN) from Azure.
-1. {YOUR-RESOURCE-ACCOUNT-GUID} parameter in the RURI, is the oid value returned by the Graph API from the previous step. Alternatively for one off manual provisioning, the [Get-CsOnlineApplicationInstance (MicrosoftTeamsPowerShell)](/powershell/module/teams/get-csonlineapplicationinstance) cmdlet returns the ObjectId and that ID is the YOUR-RESOURCE-ACCOUNT-GUID. 
-1. The {TENANT-GUID} in the RURI path is the Teams Tenant GUID.
-1. The {principalType} in the body is `teamsResourceAccount` because we're consenting to a Teams Resource Account for Teams Phone Extensibility.
+1. The `{YOUR-ACS-RESOURCE-ENDPOINT}` in the request URI (RURI) path is the Azure Communication Services Resource fully qualified domain name (FQDN) from Azure.
+1. The `{YOUR-RESOURCE-ACCOUNT-GUID}` parameter in the RURI is the oid value returned by the Graph API from the previous step. Alternatively for one off manual provisioning, the [Get-CsOnlineApplicationInstance (MicrosoftTeamsPowerShell)](/powershell/module/teams/get-csonlineapplicationinstance) cmdlet returns the `ObjectId` and that ID is the `YOUR-RESOURCE-ACCOUNT-GUID`. 
+1. The `{TENANT-GUID}` in the RURI path is the Teams Tenant GUID.
+1. The `{principalType}` in the body is `teamsResourceAccount` because we're consenting to a Teams Resource Account for Teams Phone Extensibility.
 
 This API supports Azure Communication Services hash-based message authentication code (HMAC) with a Connection String or Microsoft Entra ID Managed Identity. 
 
 Query definition: 
 
-> https://{YOUR-ACS-RESOURCE-ENDPOINT}/access/teamsExtension/tenants/{TENANT-GUID}/assignments/{YOUR-RESOURCE-ACCOUNT-GUID}?api-version=2025-03-02-preview 
-
+```http
+https://{YOUR-ACS-RESOURCE-ENDPOINT}/access/teamsExtension/tenants/{TENANT-GUID}/assignments/{YOUR-RESOURCE-ACCOUNT-GUID}?api-version=2025-03-02-preview 
+```
 
 Example to set consent: 
 
@@ -104,7 +105,7 @@ You must register your application for `TeamsExtension.ManageCalls` permission f
 3. From the **Add Permissions** menu, select **Azure Communication Services**.
 4. Select the permission `TeamsExtension.ManageCalls`, then select **Add permissions**.
 
-:::image type="content" source="./media/active-directory-permissions.png" alt-text="Screen capture showing how to add TeamsExtension.ManageCalls permission to the Microsoft Entra application you just created."  lightbox="./media/active-directory-permissions.png":::
+   :::image type="content" source="media/active-directory-permissions.png" alt-text="Screen capture showing how to add TeamsExtension.ManageCalls permission to the Microsoft Entra ID application you just created."  lightbox="media/active-directory-permissions.png":::
 
 5. Grant admin consent for `TeamsExtension.ManageCalls` permission.
 

articles/communication-services/quickstarts/tpe/media/teams-phone-extensibility-app-registration.png

@@ -54,7 +54,7 @@ PUT {endpoint}/access/teamsExtension/tenants/87d349ed-44d7-43e1-9a83-5f2406dee5b
 }
 ```
 
-The {principalType} needs to be `teamsResourceAccount`.
+The `{principalType}` needs to be `teamsResourceAccount`.
 
 ### Response
 

articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md

@@ -24,9 +24,9 @@ This article describes how an independent software vendor (ISV) can provision Te
 - ISV’s Customer has access to Microsoft 365 Admin Center.
 - ISV has access to change Azure Communication Services Resource settings.
 - You grant Teams Tenant access to a CCaaS service for Graph API usage.
-- ISV is using the .NET ACS Call Automation SDK version 1.5.0-beta.1
-- ISV is using the JavaScript ACS Call Automation SDK version 1.5.0-beta.2
-- ISV is using the JavaScript ACS Client SDK version 1.36.1-beta.1
+- ISV is using the .NET ACS Call Automation SDK version 1.5.0-beta.1.
+- ISV is using the JavaScript ACS Call Automation SDK version 1.5.0-beta.2.
+- ISV is using the JavaScript ACS Client SDK version 1.36.1-beta.1.
 
 
 ## Quick start
@@ -35,26 +35,45 @@ The rest of this article describes quick starts for two different personas: CCaa
 
 ### CCaaS Developer: Provision the AppID (Application ID)
 
-Before you can create a bot, you need to register an `ApplicationID` using steps 1 through 4 in [Registering a calling bot](https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/articles/calls/register-calling-bot.html#registering-an-app-registration).
+Before you can create a bot, you need to register an Application ID.
+
+1. From the Azure portal, open **App Registrations**.
+
+    :::image type="content" source="media/teams-phone-extensibility-app-registration.png" alt-text="Screen capture showing the Azure portal with App registration selected from services."  lightbox="media/teams-phone-extensibility-app-registration.png":::
+
+2. Select **New registration**.
+3. Complete the required fields and click **Register**.
+4. When the portal completes the resource, click **Go to resource**.
+5. Record the values for the **Application (client) ID** and **Directory (tenant) ID**.
+
+    :::image type="content" source="media/teams-phone-extensibility-app-registration-resources.png" alt-text="Screen capture showing the Azure portal App registrations resource displaying Essentials including Application (client) ID and Directory (tenant) ID."  lightbox="media/teams-phone-extensibility-app-registration-resources.png":::
+
+6. Open **Certificates & secrets**. Create new a client secret and record the certificate and secret ID values.
+
+For more information, see [Registering a calling bot](https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/articles/calls/register-calling-bot.html#registering-an-app-registration).
 
 ### CCaaS Developer: Create the Bot 
 
-Once you create the `AppID`, Teams Phone system also uses the current process as defined for Graph to create a bot. Complete steps 1 through 4 in [Registering a calling bot](https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/articles/calls/register-calling-bot.html#registering-an-app-registration).
+Once you create the `AppID`, Teams Phone system also uses the current process as defined for Graph to create a bot.
 
 Alternatively, you can complete the following steps to create just the bot after you create an  Application ID using the Azure CLI.
 
-1. Download Azure CLI
-1. Sign in with your Azure account used for the preceding App Registration:  
+1. Download Azure CLI.
+2. Sign in with your Azure account used for the preceding App Registration: 
+
     ```azurecli
     az login 
     ```
-1. If not already, Install `Az.BotService`:  
+
+3. If not already installed, install `Az.BotService`:  
+
     ```azurecli
     Install-Module Az.BotService -AllowClobber 
     ```
-1. Provision the bot using the following command. For more information, see [Publish a bot with Azure PowerShell - Azure AI Bot Service - Bot Service](/azure/bot-service/powershell/bot-builder-powershell-quickstart):
 
-If your environment is already provisioned, skip these steps.
+4. Provision the bot using the following command. For more information, see [Publish a bot with Azure PowerShell - Azure AI Bot Service - Bot Service](/azure/bot-service/powershell/bot-builder-powershell-quickstart):
+
+If your environment is already provisioned, skip the following steps.
 
 ```azurecli
 Connect-AzAccount 
@@ -488,10 +507,11 @@ StartRecordingOptions recordingOptions = new StartRecordingOptions("<callConnect
 Response<RecordingStateResult> response = await callAutomationClient.GetCallRecording()
 .StartAsync(recordingOptions);
 ```
-> [!NOTE]
-> Recording started with connection Id is started async (204 response code) and recording state change is updated via call back event (Microsoft.Communication.RecordingStateChanged) received on RecordingStateCallbackUri.
-Additionally any failures to start recording is reported via a new callback event (Microsoft.Communication.StartRecordingFailed) received on RecordingStateCallbackUri.
 
+> [!NOTE]
+> Recording started with connection ID is started async (204 response code) and recording state change is updated via callback event `Microsoft.Communication.RecordingStateChanged` received on `RecordingStateCallbackUri`.
+>
+> In addition, any failure to start recording is reported via a new callback event `Microsoft.Communication.StartRecordingFailed` received on `RecordingStateCallbackUri`.
 
 ## Alpha SDKs