Merge pull request #247594 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 8/8

Author: ttorble

articles/ai-services/document-intelligence/how-to-guides/includes/v3-0/javascript-sdk.md

@@ -589,12 +589,12 @@ async function main() {
  } = await poller.pollUntilDone();
 
   if (result) {
-    The identity document model has multiple document types, so we need to know which document type was actually
+// The identity document model has multiple document types, so we need to know which document type was actually
     extracted.
     if (result.docType === "idDocument.driverLicense") {
       const { FirstName, LastName, DocumentNumber, DateOfBirth, DateOfExpiration, Height, Weight, EyeColor, Endorsements, Restrictions, VehicleClassifications} = result.fields;
 
-      For the sake of the example, we'll only show a few of the fields that are produced.
+// For the sake of the example, we'll only show a few of the fields that are produced.
       console.log("Extracted a Driver License:");
       console.log("  Name:", FirstName && FirstName.content, LastName && LastName.content);
       console.log("  License No.:", DocumentNumber && DocumentNumber.content);
@@ -607,7 +607,7 @@ async function main() {
       console.log("  Endorsements:", Endorsements && Endorsements.content);
       console.log("  Class:", VehicleClassifications && VehicleClassifications.content);
     } else if (result.docType === "idDocument.passport") {
-      The passport document type extracts and parses the Passport's machine-readable zone
+// The passport document type extracts and parses the Passport's machine-readable zone
       if (!result.fields.machineReadableZone) {
         throw new Error("No Machine Readable Zone extracted from passport.");
       }
@@ -630,7 +630,7 @@ async function main() {
       console.log("  Issuer:", CountryRegion && CountryRegion.content);
       console.log("  Expiration Date:", DateOfExpiration && DateOfExpiration.content);
     } else {
-      The only reason this would happen is if the client library's schema for the prebuilt identity document model is
+// The only reason this would happen is if the client library's schema for the prebuilt identity document model is
       out of date, and a new document type has been introduced.
       console.error("Unknown document type in result:", result);
     }

articles/ai-services/openai/concepts/use-your-data.md

@@ -152,9 +152,24 @@ Avoid asking long questions and break them down into multiple questions if possi
 
 * If you have documents in multiple languages, we recommend building a new index for each language and connecting them separately to Azure OpenAI.  
 
-### Using the web app
+### Deploying the model
 
-You can use the available web app to interact with your model using a graphical user interface, which you can deploy using either [Azure OpenAI studio](../use-your-data-quickstart.md?pivots=programming-language-studio#deploy-a-web-app) or a [manual deployment](https://github.com/microsoft/sample-app-aoai-chatGPT). 
+After you connect Azure OpenAI to your data, you can deploy it using the **Deploy to** button in Azure OpenAI studio.
+
+:::image type="content" source="../media/use-your-data/deploy-model.png" alt-text="A screenshot showing the model deployment button in Azure OpenAI Studio." lightbox="../media/use-your-data/deploy-model.png":::
+
+#### Using Power Virtual Agents
+
+You can deploy your model to [Power Virtual Agents](/power-virtual-agents/fundamentals-what-is-power-virtual-agents) directly from Azure OpenAI studio, enabling you to bring conversational experiences to various data stores like public websites, SharePoint, OneDrive, and more. Power Virtual Agents acts as a conversational and generative AI platform, making the process of creating, publishing and deploying a bot to any number of channels simple and accessible.
+
+While Power Virtual Agents has features that leverage Azure OpenAI such as [generative answers](/power-virtual-agents/nlu-boost-conversations), deploying a model grounded on your data lets you create a chatbot that will respond using your data, and connect it to the Power Platform. For more information, see [Use a connection to Azure OpenAI on your data](/power-virtual-agents/nlu-generative-answers-azure-openai).
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RW192hF]
+
+
+#### Using the web app
+
+You can also use the available standalone web app to interact with your model using a graphical user interface, which you can deploy using either Azure OpenAI studio or a [manual deployment](https://github.com/microsoft/sample-app-aoai-chatGPT). 
 
 ![A screenshot of the web app interface.](../media/use-your-data/web-app.png)
 
@@ -170,6 +185,22 @@ When customizing the app, we recommend:
 
 - Pulling changes from the `main` branch for the web app's source code frequently to ensure you have the latest bug fixes and improvements.
 
+#### Important considerations
+
+- Publishing creates an Azure App Service in your subscription. It may incur costs depending on the 
+[pricing plan](https://azure.microsoft.com/pricing/details/app-service/windows/) you select. When you're done with your app, you can delete it from the Azure portal.
+- You can [customize](../concepts/use-your-data.md#using-the-web-app) the frontend and backend logic of the web app.
+- By default, the app will only be accessible to you. To add authentication (for example, restrict access to the app to members of your Azure tenant):
+
+    1. Go to the [Azure portal](https://portal.azure.com/#home) and search for the app name you specified during publishing. Select the web app, and go to the **Authentication** tab on the left navigation menu. Then select **Add an identity provider**. 
+    
+        :::image type="content" source="../media/quickstarts/web-app-authentication.png" alt-text="Screenshot of the authentication page in the Azure portal." lightbox="../media/quickstarts/web-app-authentication.png":::
+
+    1. Select Microsoft as the identity provider. The default settings on this page will restrict the app to your tenant only, so you don't need to change anything else here. Then select **Add**
+    
+    Now users will be asked to sign in with their Azure Active Directory account to be able to access your app. You can follow a similar process to add another identity provider if you prefer. The app doesn't use the user's login information in any other way other than verifying they are a member of your tenant.
+
+
 ### Using the API
 
 Consider setting the following parameters even if they are optional for using the API.

articles/ai-services/openai/includes/deploy-web-app.md

@@ -9,12 +9,16 @@ ms.topic: include
 ms.date: 06/15/2023
 ---
 
-## Deploy a web app
+## Deploy your model
 
 Once you're satisfied with the experience in Azure OpenAI studio, you can deploy a web app directly from the 
 Studio by selecting the **Deploy to** button. 
 
-:::image type="content" source="../media/quickstarts/chatgpt-playground-publish-web-app.png" alt-text="A screenshot showing the button to publish a web app in Azure AI studio." lightbox="../media/quickstarts/chatgpt-playground-publish-web-app.png":::
+:::image type="content" source="../media/use-your-data/deploy-model.png" alt-text="A screenshot showing the model deployment button in Azure OpenAI Studio." lightbox="../media/use-your-data/deploy-model.png":::
+
+This gives you the option to either [deploy the model](../concepts/use-your-data.md#deploying-the-model) as a standalone web application, or to Power Virtual Agents.   
+
+As an example, if you choose to deploy a web app:
 
 The first time you deploy a web app, you should select **Create a new web app**. Choose a name for the app, which will 
 become part of the app URL. For example, `https://<appname>.azurewebsites.net`. 
@@ -23,5 +27,6 @@ Select your subscription, resource group, location, and pricing plan for the pub
 update an existing app, select **Publish to an existing web app** and choose the name of your previous 
 app from the dropdown menu.
 
+If you choose to deploy a web app, see the [important considerations](../concepts/use-your-data.md#important-considerations) for using it.
 > [!div class="nextstepaction"]
-> [I ran into an issue with the web app.](https://microsoft.qualtrics.com/jfe/form/SV_0Cl5zkG3CnDjq6O?PLanguage=STUDIO&Pillar=AOAI&Product=ownData&Page=quickstart&Section=Create-sample-app)
+> [I ran into an issue with deploying the model.](https://microsoft.qualtrics.com/jfe/form/SV_0Cl5zkG3CnDjq6O?PLanguage=STUDIO&Pillar=AOAI&Product=ownData&Page=quickstart&Section=Create-sample-app)

articles/ai-services/openai/includes/use-your-data-studio.md

@@ -61,18 +61,3 @@ You can experiment with the configuration settings such as temperature and pre-r
 
 [!INCLUDE [deploy-web-app](deploy-web-app.md)]
 
-
-### Important considerations
-
-- Publishing creates an Azure App Service in your subscription. It may incur costs depending on the 
-[pricing plan](https://azure.microsoft.com/pricing/details/app-service/windows/) you select. When you're done with your app, you can delete it from the Azure portal.
-- You can [customize](../concepts/use-your-data.md#using-the-web-app) the frontend and backend logic of the web app.
-- By default, the app will only be accessible to you. To add authentication (for example, restrict access to the app to members of your Azure tenant):
-
-    1. Go to the [Azure portal](https://portal.azure.com/#home) and search for the app name you specified during publishing. Select the web app, and go to the **Authentication** tab on the left navigation menu. Then select **Add an identity provider**. 
-    
-        :::image type="content" source="../media/quickstarts/web-app-authentication.png" alt-text="Screenshot of the authentication page in the Azure portal." lightbox="../media/quickstarts/web-app-authentication.png":::
-
-    1. Select Microsoft as the identity provider. The default settings on this page will restrict the app to your tenant only, so you don't need to change anything else here. Then select **Add**
-    
-    Now users will be asked to sign in with their Azure Active Directory account to be able to access your app. You can follow a similar process to add another identity provider if you prefer. The app doesn't use the user's login information in any other way other than verifying they are a member of your tenant.

articles/ai-services/openai/media/use-your-data/deploy-model.png

@@ -1,15 +1,15 @@
 ---
-title: Use the application routing add-on with Azure Kubernetes Service (AKS) clusters (preview)
+title: Azure Kubernetes Service (AKS) ingress with the application routing add-on (preview)
 description: Use the application routing add-on to securely access applications deployed on Azure Kubernetes Service (AKS).
 ms.subservice: aks-networking
 ms.custom: devx-track-azurecli
-author: sabbour
+author: asudbring
 ms.topic: how-to
-ms.date: 05/04/2023
-ms.author: asabbour
+ms.date: 08/07/2023
+ms.author: allensu
 ---
 
-# Use the application routing add-on with Azure Kubernetes Service (AKS) clusters (preview)
+# Azure Kubernetes Service (AKS) ingress with the application routing add-on (preview)
 
 The application routing add-on configures an [ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/) in your Azure Kubernetes Service (AKS) cluster with SSL termination through certificates stored in Azure Key Vault. It can optionally integrate with Open Service Mesh (OSM) for end-to-end encryption of inter-cluster communication using mutual TLS (mTLS). When you deploy ingresses, the add-on creates publicly accessible DNS names for endpoints on an Azure DNS zone.
 

articles/aks/app-routing.md

@@ -1,15 +1,16 @@
 ---
-title: Create an ingress controller in Azure Kubernetes Service (AKS)
+title: Create an unmanaged ingress controller
+titleSuffix: Azure Kubernetes Service
 description: Learn how to create and configure an ingress controller in an Azure Kubernetes Service (AKS) cluster.
 author: asudbring
 ms.author: allensu
 ms.subservice: aks-networking
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 02/23/2023
+ms.date: 08/07/2023
 ---
 
-# Create an ingress controller in Azure Kubernetes Service (AKS)
+# Create an unmanaged ingress controller
 
 An ingress controller is a piece of software that provides reverse proxy, configurable traffic routing, and TLS termination for Kubernetes services. Kubernetes ingress resources are used to configure the ingress rules and routes for individual Kubernetes services. When you use an ingress controller and ingress rules, a single IP address can be used to route traffic to multiple services in a Kubernetes cluster.
 

articles/aks/ingress-basic.md

@@ -1,13 +1,15 @@
 ---
-title: Deploy external or internal ingresses for Istio service mesh add-on for Azure Kubernetes Service (preview)
+title: Azure Kubernetes Service (AKS) external or internal ingresses for Istio service mesh add-on (preview)
 description: Deploy external or internal ingresses for Istio service mesh add-on for Azure Kubernetes Service (preview)
-ms.topic: article
-ms.custom:
-ms.date: 04/09/2023
-ms.author: shasb
+ms.topic: how-to
+ms.service: azure-kubernetes-service
+ms.subservice: aks-networking
+author: asudbring
+ms.date: 08/07/2023
+ms.author: allensu
 ---
 
-# Deploy external or internal ingresses for Istio service mesh add-on for Azure Kubernetes Service (preview)
+# Azure Kubernetes Service (AKS) external or internal ingresses for Istio service mesh add-on deployment (preview)
 
 This article shows you how to deploy external or internal ingresses for Istio service mesh add-on for Azure Kubernetes Service (AKS) cluster.
 

articles/aks/istio-deploy-ingress.md

@@ -122,6 +122,65 @@ The following example injects a singleton service dependency:
 
 This code requires `using Microsoft.Extensions.DependencyInjection;`. To learn more, see [Dependency injection in ASP.NET Core](/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-5.0&preserve-view=true).
 
+#### Register Azure clients
+
+Dependency injection can be used to interact with other Azure services. You can inject clients from the [Azure SDK for .NET](/dotnet/azure/sdk/azure-sdk-for-dotnet) using the [Microsoft.Extensions.Azure](https://www.nuget.org/packages/Microsoft.Extensions.Azure) package. After installing the package, [register the clients](/dotnet/azure/sdk/dependency-injection#register-clients) by calling `AddAzureClients()` on the service collection in `Program.cs`. The following example configures a [named client](/dotnet/azure/sdk/dependency-injection#configure-multiple-service-clients-with-different-names) for Azure Blobs:
+
+```csharp
+using Microsoft.Extensions.Azure;
+using Microsoft.Extensions.Hosting;
+
+var host = new HostBuilder()
+    .ConfigureFunctionsWorkerDefaults()
+    .ConfigureServices((hostContext, services) =>
+    {
+        services.AddAzureClients(clientBuilder =>
+        {
+            clientBuilder.AddBlobServiceClient(hostContext.Configuration.GetSection("MyStorageConnection"))
+                .WithName("copierOutputBlob");
+        });
+    })
+    .Build();
+
+host.Run();
+```
+
+The following example shows how we can use this registration and [SDK types](#sdk-types) to copy blob contents as a stream from one container to another using an injected client:
+
+```csharp
+using Microsoft.Extensions.Azure;
+using Microsoft.Extensions.Logging;
+
+namespace MyFunctionApp
+{
+    public class BlobCopier
+    {
+        private readonly ILogger<BlobCopier> _logger;
+        private readonly BlobContainerClient _copyContainerClient;
+
+        public BlobCopier(ILogger<BlobCopier> logger, IAzureClientFactory<BlobServiceClient> blobClientFactory)
+        {
+            _logger = logger;
+            _copyContainerClient = blobClientFactory.CreateClient("copierOutputBlob").GetBlobContainerClient("samples-workitems-copy");
+            _copyContainerClient.CreateIfNotExists();
+        }
+
+        [Function("BlobCopier")]
+        public async Task Run([BlobTrigger("samples-workitems/{name}", Connection = "MyStorageConnection")] Stream myBlob, string name)
+        {
+            await _copyContainerClient.UploadBlobAsync(name, myBlob);
+            _logger.LogInformation($"Blob {name} copied!");
+        }
+
+    }
+}
+```
+
+The [ILogger&lt;T&gt;] in this example was also obtained through dependency injection. It is registered automatically. To learn more about configuration options for logging, see [Logging](#logging).
+
+> [!TIP]
+> The example used a literal string for the name of the client in both `Program.cs` and the function. Consider instead using a shared constant string defined on the function class. For example, you could add `public const string CopyStorageClientName = nameof(_copyContainerClient);` and then reference `BlobCopier.CopyStorageClientName` in both locations. You could similarly define the configuration section name with the function rather than in `Program.cs`.
+
 ### Middleware
 
 .NET isolated also supports middleware registration, again by using a model similar to what exists in ASP.NET. This model gives you the ability to inject logic into the invocation pipeline, and before and after functions execute.
@@ -246,7 +305,7 @@ Each trigger and binding extension also has its own minimum version requirement,
 [eventhub-sdk-types]: ./functions-bindings-event-hubs.md?tabs=isolated-process%2Cextensionv5&pivots=programming-language-csharp#binding-types
 [servicebus-sdk-types]: ./functions-bindings-service-bus.md?tabs=isolated-process%2Cextensionv5&pivots=programming-language-csharp#binding-types
 
-<sup>1</sup> For output scenarios in which you would use an SDK type, you should create and work with SDK clients directly instead of using an output binding.
+<sup>1</sup> For output scenarios in which you would use an SDK type, you should create and work with SDK clients directly instead of using an output binding. See [Register Azure clients](#register-azure-clients) for an example of how to do this with dependency injection.
 
 <sup>2</sup> The Service Bus trigger does not yet support message settlement scenarios for the isolated model.
 
@@ -502,6 +561,7 @@ Because your isolated worker process app runs outside the Functions runtime, you
 [FunctionContext]: /dotnet/api/microsoft.azure.functions.worker.functioncontext?view=azure-dotnet&preserve-view=true
 [ILogger]: /dotnet/api/microsoft.extensions.logging.ilogger
 [ILogger&lt;T&gt;]: /dotnet/api/microsoft.extensions.logging.ilogger-1
+[ILoggerFactory]: /dotnet/api/microsoft.extensions.logging.iloggerfactory
 [GetLogger]: /dotnet/api/microsoft.azure.functions.worker.functioncontextloggerextensions.getlogger
 [GetLogger&lt;T&gt;]: /dotnet/api/microsoft.azure.functions.worker.functioncontextloggerextensions.getlogger#microsoft-azure-functions-worker-functioncontextloggerextensions-getlogger-1
 [HttpRequestData]: /dotnet/api/microsoft.azure.functions.worker.http.httprequestdata?view=azure-dotnet&preserve-view=true

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -517,7 +517,7 @@ Connection string for storage account where the function app code and configurat
 |---|------------|
 |WEBSITE_CONTENTAZUREFILECONNECTIONSTRING|`DefaultEndpointsProtocol=https;AccountName=...`|
 
-This setting is required for Consumption plan apps on Windows and for Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. 
+This setting is required for Consumption plan apps on Windows and for Elastic Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. 
 
 Changing or removing this setting may cause your function app to not start. To learn more, see [this troubleshooting article](functions-recover-storage-account.md#storage-account-application-settings-were-deleted).