Merge pull request #303019 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-19 05:00 UTC

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

articles/app-service/configure-authentication-provider-aad.md

@@ -301,7 +301,7 @@ Requests that fail these built-in checks get an HTTP `403 Forbidden` response.
 
 [fic-config]: #use-a-managed-identity-instead-of-a-secret-preview
 
-Instead of configuring a client secret for your app registration, you can [configure an application to trust a managed identity (preview)][entra-fic]. Using an identity instead of a secret means you don't have to manage a secret. You don't have secret expiration events to handle, and you don't have the same level of risk associated with possibly disclosing or leaking that secret.
+Instead of configuring a client secret for your app registration, you can [configure an application to trust a managed identity][entra-fic]. Using an identity instead of a secret means you don't have to manage a secret. You don't have secret expiration events to handle, and you don't have the same level of risk associated with possibly disclosing or leaking that secret.
 
 The identity allows you to create a *federated identity credential*, which can be used instead of a client secret as a *client assertion*. This approach is available only for workforce configurations. The built-in authentication feature currently supports federated identity credentials as a preview.
 
@@ -313,6 +313,7 @@ You can use the steps in this section to configure your App Service or Azure Fun
 
     > [!IMPORTANT]
     > The user-assigned managed identity that you create should only be assigned to the App Service or Azure Functions application through this registration. If you assign the identity to another resource, you're giving that resource unnecessary access to your app registration.
+
 1. Note down the **Object ID** and **Client ID** values of the managed identity. You'll need the object ID to create a federated identity credential in the next step. You'll use the managed identity's client ID in a later step.
 
 1. Follow the Microsoft Entra ID [instructions to configure a federated identity credential on an existing application](/entra/workload-id/workload-identity-federation-config-app-trust-managed-identity#configure-a-federated-identity-credential-on-an-existing-application). Those instructions also include sections for updating application code, which you can skip.

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md

@@ -8,7 +8,7 @@ ms.author: azfuncdf
 zone_pivot_groups: df-languages
 ---
 
-# Orchestration Versioning
+# Orchestration Versioning (preview)
 
 A key area to consider when using a durable orchestration system is how to handle the upgrading/downgrading of orchestrations. When an orchestration is interrupted and later resumed (for instance, during a host update), Durable Task Scheduler will replay the events of the orchestration. This is done to ensure reliability - the system replays to ensure all previous steps were executed successfully before the next step is taken - which is a core promise of the durable execution paradigm. So, if an orchestration changes between deployments, the steps it takes may no longer be the same. If this does happen, the system will throw a `NonDeterministicError` instead of allowing the orchestration to continue. 
 
@@ -44,7 +44,7 @@ In order for an orchestration to have a version, it must first be set in the cli
 ::: zone pivot="csharp"
 
 > [!NOTE]
-> Available in the .NET SDK since v1.9.0.
+> Available in the .NET SDK (Microsoft.DurableTask.Client.AzureManaged) since v1.9.0.
 
 ```csharp
 builder.Services.AddDurableTaskClient(builder =>
@@ -59,7 +59,7 @@ builder.Services.AddDurableTaskClient(builder =>
 ::: zone pivot="java"
 
 > [!NOTE]
-> Available in the Java SDK since v1.6.0.
+> Available in the Java SDK (com.microsoft:durabletask-client) since v1.6.0.
 
 ```java
 public DurableTaskClient durableTaskClient(DurableTaskProperties properties) {
@@ -166,6 +166,9 @@ Similar to the client versioning, these are all set via the standard host builde
 
 ::: zone pivot="csharp"
 
+> [!NOTE]
+> Available in the .NET SDK (Microsoft.DurableTask.Worker.AzureManaged) since v1.9.0.
+
 ```csharp
 builder.Services.AddDurableTaskWorker(builder =>
 {
@@ -185,6 +188,9 @@ builder.Services.AddDurableTaskWorker(builder =>
 
 ::: zone pivot="java"
 
+> [!NOTE]
+> Available in the Java SDK (com.microsoft:durabletask-client) since v1.6.0.
+
 ```java
 private static DurableTaskGrpcWorker createTaskHubServer() {
     DurableTaskGrpcWorkerBuilder builder = new DurableTaskGrpcWorkerBuilder();

articles/communication-services/quickstarts/email/includes/add-multiple-senders-net.md

@@ -29,13 +29,11 @@ dotnet add package Azure.ResourceManager.Communication
 Set the environment variable `AZURE_SUBSCRIPTION_ID` with the subscription ID of the subscription your Domain and Email resources are in. Run the code sample to initialize the management client.
 
 ```csharp
-using System;
-using System.Threading.Tasks;
 using Azure.Core;
 using Azure.Identity;
 using Azure.ResourceManager;
-using Azure.ResourceManager.Compute;
-using Azure.ResourceManager.Resources;
+using Azure.ResourceManager.Communication;
+using Azure;
 
 ArmClient client = new ArmClient(new DefaultAzureCredential());
 ```

articles/communication-services/quickstarts/email/includes/connect-domain-net.md

@@ -37,6 +37,8 @@ using Azure.Identity;
 using Azure.ResourceManager;
 using Azure.ResourceManager.Compute;
 using Azure.ResourceManager.Resources;
+using Azure.ResourceManager.Communication;
+using Azure.ResourceManager.Communication.Models;
 
 ArmClient client = new ArmClient(new DefaultAzureCredential());
 ```

articles/connectors/built-in.md

@@ -4,9 +4,9 @@ description: Learn about connectors that run natively with the runtime in Azure
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
-ms.topic: conceptual
+ms.topic: concept-article
 ms.custom: engagement-fy23
-ms.date: 12/18/2024
+ms.date: 03/18/2025
 ---
 
 # Built-in connectors in Azure Logic Apps
@@ -29,7 +29,7 @@ The following table lists the current and expanding galleries of built-in operat
 
 | Consumption | Standard |
 |-------------|----------|
-| Azure API Management <br>Azure App Service <br>Azure Functions <br>Azure Logic Apps <br>Batch Operations <br>Control <br>Data Operations <br>Date Time <br>Flat File <br>HTTP <br>Inline Code <br>Integration Account <br>Liquid Operations <br>Request <br>Schedule <br>Variables <br>XML Operations | AS2 (v2) <br>Azure AI Search* <br>Azure API Management <br>Azure Automation* <br>Azure Blob Storage* <br>Azure Cosmos DB* <br>Azure Event Grid Publisher* <br>Azure Event Hubs* <br>Azure File Storage* <br>Azure Functions <br>Azure Key Vault* <br>Azure OpenAI* <br>Azure Queue Storage* <br>Azure Service Bus* <br>Azure Table Storage* <br>Batch Operations <br>Control <br>Data Mapper Operations <br>Data Operations <br>Date Time <br>EDIFACT <br>File System* <br>Flat File <br>FTP* <br>HTTP <br>IBM 3270* <br>IBM CICS* <br>IBM DB2* <br>IBM Host File* <br>IBM IMS* <br>IBM MQ* <br>Inline Code <br>Integration Account <br>JDBC* <br>Liquid Operations <br>Request <br>RosettaNet <br>SAP* <br>Schedule <br>SFTP* <br>SMTP* <br>SQL Server* <br>SWIFT <br>Variables <br>Workflow Operations <br>X12 <br>XML Operations |
+| Azure API Management <br>Azure App Service <br>Azure Functions <br>Azure Logic Apps <br>Batch Operations <br>Control <br>Data Operations <br>Date Time <br>Flat File <br>HTTP <br>Inline Code <br>Integration Account <br>Liquid Operations <br>Request <br>Schedule <br>Variables <br>XML Operations | AI Operations <br>AS2 (v2) <br>Azure AI Document Intelligence* <br>Azure AI Search* <br>Azure API Management <br>Azure Automation* <br>Azure Blob Storage* <br>Azure Container App (ACA) session* <br>Azure Cosmos DB* <br>Azure Event Grid Publisher* <br>Azure Event Hubs* <br>Azure File Storage* <br>Azure Functions <br>Azure Key Vault* <br>Azure OpenAI* <br>Azure Queue Storage* <br>Azure Service Bus* <br>Azure Table Storage* <br>Batch Operations <br>Confluent* <br>Control <br>Data Mapper Operations <br>Data Operations <br>Date Time <br>EDIFACT <br>File System* <br>Flat File <br>FTP* <br>HTTP <br>IBM 3270* <br>IBM CICS* <br>IBM DB2* <br>IBM Host File* <br>IBM IMS* <br>IBM MQ* <br>Inline Code <br>Integration Account <br>JDBC* <br>Liquid Operations <br>RabbitMQ <br>Request <br>RosettaNet <br>SAP* <br>Schedule <br>SFTP* <br>SMTP* <br>SQL Server* <br>SWIFT <br>Variables <br>Workflow Operations <br>X12 <br>XML Operations |
 
 <a name="service-provider-interface-implementation"></a>
 

articles/connectors/compare-built-in-azure-connectors.md

@@ -4,7 +4,7 @@ description: Learn the differences between built-in operations and shared connec
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
-ms.topic: conceptual
+ms.topic: concept-article
 ms.date: 06/09/2025
 # Customer intent: As a developer, I want to understand the differences between built-in and Azure connectors in Azure Logic Apps (Standard).
 ---

articles/connectors/connectors-create-api-informix.md

@@ -4,8 +4,8 @@ description: Learn about the impact that Google security and privacy policies ha
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
-ms.topic: conceptual
-ms.date: 01/04/2024
+ms.topic: concept-article
+ms.date: 05/04/2025
 ---
 
 # Data security and privacy policies for Google connectors in Azure Logic Apps

articles/connectors/connectors-google-data-security-privacy-policy.md

@@ -4,8 +4,8 @@ description: Create and run recurring tasks that handle contiguous data by using
 services: logic-apps
 ms.suite: integration
 ms.reviewer: deli, azla
-ms.topic: conceptual
-ms.date: 01/04/2024
+ms.topic: how-to
+ms.date: 06/04/2025
 ---
 
 # Schedule and run tasks for contiguous data by using the Sliding Window trigger in Azure Logic Apps

articles/connectors/connectors-native-sliding-window.md

@@ -4,7 +4,7 @@ description: Learn how connectors in Azure Logic Apps help you access data, even
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
-ms.topic: conceptual
+ms.topic: concept-article
 ms.date: 03/27/2025
 # Customer intent: As a developer, I want to learn how connectors help me access data, events, and resources in other apps, services, systems, and platforms from my workflow in Azure Logic Apps.
 ---