Merge pull request #309555 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-15 12:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-netapp-files/configure-directory-server.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/07/2025
+ms.date: 12/09/2025
 ms.author: anfdocs
 ---
 # Configure LDAP directory services for Azure NetApp Files NFS volumes (preview)
@@ -121,6 +121,10 @@ You must first create the LDAP server before you can connect it to Azure NetApp
     * **Domain:** The domain name serves as the base DN. 
     * **LDAP servers:** The IP address of the LDAP server. 
     * **LDAP over TLS:** Optionally, check the box to enable LDAP over TLS for secure communication. For more information, see [Configure LDAP over TLS](configure-ldap-over-tls.md).
+      
+       > [!NOTE]
+       > To enable LDAP over TLS on multiple servers, you should generate and install the common certificate on each server and then upload the server CA certificate in the Azure portal.
+
     * **Server CA certificate:** The certification authority certificate. This option is required if you use LDAP over TLS. 
     * **Certificate CN Host:** The common name server of the host, for example contoso.server.com. 
 
@@ -141,4 +145,4 @@ You must first create the LDAP server before you can connect it to Azure NetApp
 - [Understand name mapping using LDAP](lightweight-directory-access-protocol-name-mapping.md)
 - [Understand allow local NFS users with LDAP option](lightweight-directory-access-protocol-local-users.md)
 - [Understand LDAP schemas](lightweight-directory-access-protocol-schemas.md)
-- [Create an NFS volume](azure-netapp-files-create-volumes.md)
+- [Create an NFS volume](azure-netapp-files-create-volumes.md)

articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md

@@ -59,19 +59,47 @@ Then execute the following command to add a service principal to your tenant. Do
 New-MgServicePrincipal -AppId "1fd5118e-2576-4263-8130-9503064c837a"
 ```
 
-### Error 404 subcode 580406 "Balance not found"
+---
+### Error 404 subcode 5804xx: Blocked Outbound Calls
 
-This error typically occurs when the resource account does not have an active calling plan with PAYG enabled or sufficient Communications Credits. This is required for all Outbound calling scenarios in Teams Phone Extensibility. Follow these steps to resolve the issue:
+These errors typically occur when the resource account does not have an active funding source for outbound calls. The funding source depends on the customer’s agreement type:
 
-#### 1. Sign in to Microsoft 365 Admin Center
-Log in with your **admin credentials** [https://admin.microsoft.com](https://admin.microsoft.com)
+- **If the customer has an MCA agreement:**
+  - Ensure a **postpaid payment method** is in place.
+  - Ensure the tenant has a **Microsoft Teams Calling Plan (Pay-As-You-Go)** license.
+  - Ensure the **Pay-As-You-Go Calling Plan license is assigned to the resource account**.
+
+- **If the customer has an older agreement:**
+  - Ensure the tenant has a **Communications Credits** license.
+  - Ensure the **Communications Credits balance is positive** (funds are loaded).
+
+Outbound calling in Teams Phone Extensibility requires one of these funding sources to be correctly configured. If not set properly, you may see one of the below error subcodes:
+
+| Error Code | Meaning                                      | Fix                                                                 |
+|------------|---------------------------------------------|--------------------------------------------------------------------|
+| 580406     | Balance not found                          | Check funding source setup (MCA or Communications Credits)        |
+| 580462     | No enabled tenant capabilities             | Assign Communications Credits license to tenant                   |
+| 580464     | No enabled user capabilities               | Assign Communications Credits license to user                    
 
-#### 2. Add Pay-As-You-Go Calling Plan
-- Navigate to **Marketplace → All Products**.
-- Search for **Microsoft Teams Calling Plan (Pay-As-You-Go)**.
-- Select the appropriate **Pay-As-You-Go Calling Plan Zone (Zone 1 or Zone 2)** based on your location.
-- Add the plan under **Add-ons**.  
-More details: [Learn more about Calling Plans PAYG](/microsoftteams/calling-plans-for-office-365#pay-as-you-go-calling-plan)
+You can follow the below steps to solve this:
+
+#### 1. Sign in to Microsoft 365 Admin Center
+Log in with your **admin credentials**: [https://admin.microsoft.com](https://admin.microsoft.com)
+
+#### 2. Verify agreement type and funding source
+- For **MCA agreements**:
+  - Confirm **postpaid payment method** is active.
+  - Navigate to **Marketplace → All Products**.
+  - Search for **Microsoft Teams Calling Plan (Pay-As-You-Go)**.
+  - Select the appropriate **Pay-As-You-Go Calling Plan Zone (Zone 1 or Zone 2)** based on your location.
+  - Add the plan under **Add-ons**.  
+  More details: [Learn more about Calling Plans pay-as-you-go](/microsoftteams/calling-plans-for-office-365#pay-as-you-go-calling-plan)
+
+- For **older agreements**:
+  - Navigate to **Marketplace → All Products** and purchase **Communications Credits**.
+  - Add funds to ensure a positive balance.
+  - Enable **Auto-Recharge** under **Billing → Your Products → Communications Credits**.  
+  More details: [Set up Communications Credits](/microsoftteams/set-up-communications-credits-for-your-organization)
 
 #### 3. Assign Licenses to Resource Account
 - Go to **Users → Active Users**.
@@ -81,19 +109,17 @@ More details: [Learn more about Calling Plans PAYG](/microsoftteams/calling-plan
 - **Important:** Remove any other conflicting calling plans.  
 More details: [Assign licenses to users](/microsoft-365/admin/manage/assign-licenses-to-users)
 
-#### 4. Purchase Communications Credits
-- Go to **Marketplace → All Products**.
-- Search for **Communications Credits** under **Add-ons**.
-- Purchase credits and add funds.  
-More details: [What are Communications Credits?](/microsoftteams/what-are-communications-credits)
 
-#### 5. Enable Auto-Recharge
-- After purchase, go to **Billing → Your Products**.
-- Select **Communications Credits**.
-- Turn **Auto-Recharge ON** to avoid running out of balance.  
-More details: [Set up Communications Credits](/microsoftteams/set-up-communications-credits-for-your-organization)
+---
+### Error 403 subcode 510586: Blocked Outbound Calls from Operator Connect Carrier
+
+This error indicates that outbound PSTN calls are being blocked by your Operator Connect carrier. This typically occurs when there are restrictions or issues with your carrier’s configuration or account status. This can be caused by:
+- Carrier-imposed restrictions on outbound calling.
+- Account suspension or insufficient balance with the carrier.
+- Incorrect configuration of Operator Connect settings.
 
 
+---
 ### Error 400 code 8523 Invalid request: SourceCallerIdNumber and SourceDisplayName aren't supported
 
 Trying to set caller display name caller ID via CallInvite options return an error:
@@ -106,7 +132,7 @@ These parameters aren't currently supported in Teams Phone extensibility. You ne
 ```csharp
 await answerCallContext.CallConnection.AddParticipantAsync(new CallInvite(new PhoneNumberIdentifier("+133333333"),null));
 ```
-
+---
 ### Error 422 Invalid CommunicationUser identifier specified
 
 When your app places an OBO call, the client gets this error if you try to place a call with a phone number. 
@@ -128,6 +154,7 @@ Calling OBO feature doesn't support calling from a phone number. In `onBehalfOfO
 
 ```
 
+---
 ### Error 408 subcode 10057 `addParticipants` failed for participant `8:acs`
 
 The issue appears when adding dual persona agent and getting an `AddParticipantFailed` event error with the following message:
@@ -142,6 +169,7 @@ The issue appears when adding dual persona agent and getting an `AddParticipantF
 
 The most common cause is that you're minting a Custom Teams Endpoint (CTE) token and the client is registering with that token with an `8:orgid` MRI as opposed to a dual persona token. This problem is causing the client to not receive the calls since the MRI was `8:orgid` and the server adding a dual persona MRI with `8:acs`.
 
+---
 ### Error 403 code `UserLicenseNotPresentForbidden` when agent logs in to client application
 
 The issue appears when agent attempts to sign in to the agent application.
@@ -152,18 +180,22 @@ The issue appears when agent attempts to sign in to the agent application.
 
 This issue appears if the agent doesn't have a Teams license assigned or is disabled in Teams. Add the appropriate license and validate if user isn't disabled for Teams access and has all the required [Prerequisites](../../../quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md#prerequisites).
 
+---
 ### Error 403 subcode 10105 Connecting Call end reason=NoPermission
 
 The most common root cause of this error is a misconfiguration of the 3P Azure Bot. Follow the steps as defined in this [Teams Phone extensibility](../../../quickstarts/tpe/teams-phone-extensibility-quickstart.md#ccaas-developer-provision-the-appid-application-id), specifically enable the Teams channel.
 
+---
 ### Error 400 Bad Requests when adding a Teams Channel in Azure Bot
 
 This issue generally arises if the bot was created with a reserved Microsoft Entra App ID. Delete your bot and recreate it with your Microsoft Entra App ID created or used in [Create Bot](../../../quickstarts/tpe/teams-phone-extensibility-quickstart.md#ccaas-developer-create-the-bot).
 
+---
 ### No Incoming Call notification in Call Automation application and a busy signal is heard instead of custom greeting when calling a Teams Service Number
 
 This issue arises when the provisioning of the Resource Account is incomplete or incorrect. Check your [Provisioning Resource Account](../../../quickstarts/tpe/teams-phone-extensibility-quickstart.md#teams-admin-provision-resource-account) and change as needed.
 
+---
 ### No Incoming Call notification in Call Automation application and no audio is heard and call disconnects when calling a Teams Service Number
 
 This issue arises when the provisioning of the Resource Account is incomplete or incorrect or failure to grant consent. Check [Provisioning Resource Account](../../../quickstarts/tpe/teams-phone-extensibility-quickstart.md#teams-admin-provision-resource-account) and [Server Consent](../../../quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md#provide-server-consent), making changes as needed.

articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-customer-agreement.md

@@ -9,6 +9,7 @@ ms.subservice: billing
 ms.topic: how-to
 ms.date: 08/18/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-arm-template, devx-track-bicep
+service.tree.id: b69a7832-2929-4f60-bf9d-c6784a865ed8
 ---
 
 # Programmatically create Azure subscriptions for a Microsoft Customer Agreement with the latest APIs

articles/cost-management-billing/troubleshoot-billing/how-to-create-azure-support-request-ea.md

@@ -10,6 +10,7 @@ ms.service: cost-management-billing
 ms.subservice: billing
 ms.custom:
 - build-2025
+service.tree.id: b69a7832-2929-4f60-bf9d-c6784a865ed8
 ---
 
 # Create an Azure support request for an Enterprise Agreement issue

articles/migrate/best-practices-least-privileged-account.md

@@ -117,7 +117,7 @@ For quick discovery of Windows servers, create a Windows user account that belon
 
 The guest user account needs permission to access the **CIMV2** namespace and its sub-namespaces in the **WMI Control** item in Control Panel. To set the access, use the following steps:
 
-1. On the target Windows server, open the **Start** menu, search for **Run**, and then select it.
+1. On the target Windows server, go to the **Start** menu, search for **Run**, and then select it.
 
 1. In the **Run** dialog, type `wmimgmt.msc` and then press the Enter key.
 

articles/migrate/cast-highlights-integration.md

@@ -25,7 +25,7 @@ Integrating CAST Highlight with Azure Migrate allows you to import code-level in
 
 ## Steps to Add CAST Highlight Code Insights in Azure Migrate
 
-1. **Open Azure Migrate & Select Application**
+1. **Go to Azure Migrate & Select Application**
    - In the Azure Migrate portal, navigate to your project.
    - Go to **Servers, Databases & Web Apps > Applications** (under **Discovery and Assessment**).
    - Locate the application (or group of VMs) you want to enrich with code insights.

articles/migrate/define-manage-applications.md

@@ -47,9 +47,9 @@ This article describes how you can use Azure Migrate to define applications runn
 
 ### Add credentials and initiate discovery
 
-1. Open the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
+1. Go to the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
 
-2. Navigate to the **Manage credentials and discovery sources** panel.
+2. Go to the **Manage credentials and discovery sources** panel.
 
 3. In **Step 1: Provide credentials for discovery source**, select on **Add credentials** to  provide credentials for the discovery source that the appliance uses to discover servers running in your environment.
 

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

@@ -71,7 +71,7 @@ The new users need to follow the below steps:
 
 ### Add credentials and initiate discovery
 
-1. Open the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
+1. Go to the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
 
 2. Navigate to the **Manage credentials and discovery sources** panel.
 

articles/migrate/how-to-discover-applications.md

@@ -49,7 +49,7 @@ In this tutorial, you learn how:
 
 ### Add credentials and initiate discovery
 
-1. Open the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
+1. Go to the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
 2. Navigate to the **Manage credentials and discovery sources** panel.
 3. In **Step 1: Provide credentials for discovery source**, select on **Add credentials** to  provide credentials for the discovery source that the appliance uses to discover servers running in your environment.
 4. In **Step 2: Provide discovery source details**, select **Add discovery source** to select the friendly name for credentials from the drop-down, specify the **IP address/FQDN** of the discovery source.

articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md

@@ -140,7 +140,7 @@ uuid                                 label       name    maxSizeInBytes
 
 ## Create Resource Manager template for replication
 
-- Open the Resource Manager template file that you downloaded in the **Identifying replication infrastructure components** step in an editor of your choice.
+- Go to the Resource Manager template file that you downloaded in the **Identifying replication infrastructure components** step in an editor of your choice.
 - Remove all resource definitions from the template except for resources that are of type *"Microsoft.RecoveryServices/vaults/replicationFabrics/replicationProtectionContainers/replicationMigrationItems"*
 - If there are multiple resource definitions of the above type, remove all but one. Remove any **dependsOn** property definitions from the resource definition.
 - At the end of this step, you should have a file that looks like the example below and has the same set of properties.