Merge pull request #272209 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/ai-services/document-intelligence/concept-invoice.md

@@ -234,6 +234,7 @@ Following are the line items extracted from an invoice in the JSON output respon
 | Amount | Number | The amount of the line item | $60.00 | 100 |
 | Description | String | The text description for the invoice line item | Consulting service | Consulting service |
 | Quantity | Number | The quantity for this invoice line item | 2 | 2 |
+| OrderQuantity | Number | The ordered quantity for this line item. May differ from the quantity shipped and invoiced | 3 | 3 |
 | UnitPrice | Number | The net or gross price (depending on the gross invoice setting of the invoice) of one unit of this item | $30.00 | 30 |
 | ProductCode | String| Product code, product number, or SKU associated with the specific line item | A123 | |
 | Unit | String| The unit of the line item, e.g,  kg, lb etc. | Hours | |
@@ -301,6 +302,28 @@ The following are the line items extracted from an invoice in the JSON output re
 | Date | date| Date corresponding to each line item. Often it's a date the line item was shipped | 3/4/2021| 2021-03-04 |
 | Tax | number | Tax associated with each line item. Possible values include tax amount, tax %, and tax Y/N | 10% | |
 
+The following are complex fields extracted from an invoice in the JSON output response:
+
+### TaxDetails
+Tax details aims at breaking down the different taxes applied to the invoice total.
+
+|Name| Type | Description | Text (line item #1) | Value (standardized output) |
+|:-----|:----|:----|:----| :----|
+| Items | string | Full string text line of the tax item | V.A.T. 15% $60.00 | |
+| Amount | number | The tax amount of the tax item | 60.00 | 60 |
+| Rate | string | The tax rate of the tax item | 15% | |
+
+### PaymentDetails
+List all the detected payment options detected on the field. 
+
+|Name| Type | Description | Text (line item #1) | Value (standardized output) |
+|:-----|:----|:----|:----| :----|
+| IBAN | string | Internal Bank Account Number | GB33BUKB20201555555555 | |
+| SWIFT | string | SWIFT code | BUKBGB22 | |
+| BPayBillerCode | string | Australian B-Pay Biller Code | 12345 | |
+| BPayReference | string | Australian B-Pay Reference Code | 98765432100 | |
+
+
 ### JSON output
 
 The JSON output has three parts:

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

@@ -79,7 +79,7 @@ Create a Node.js Express application.
 1. Install the `ai-document-intelligence` client library and `azure/identity` npm packages:
 
     ```console
-    npm i @azure/[email protected] @azure/identity
+    npm i @azure-rest/[email protected] @azure/identity
     ```
 
   Your app's *package.json* file is updated with the dependencies.
@@ -106,7 +106,7 @@ Open the `index.js` file in Visual Studio Code or your favorite IDE and select o
 ## Use the Read model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -202,7 +202,7 @@ Visit the Azure samples repository on GitHub and view the [`read` model output](
 ## Use the Layout model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -272,7 +272,7 @@ Visit the Azure samples repository on GitHub and view the [layout model output](
 ## Use the General document model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -318,7 +318,7 @@ Visit the Azure samples repository on GitHub and view the [general document mode
 ## Use the W-2 tax model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -397,7 +397,7 @@ Visit the Azure samples repository on GitHub and view the [W-2 tax model output]
 ## Use the Invoice model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -459,7 +459,7 @@ Visit the Azure samples repository on GitHub and view the [invoice model output]
 ## Use the Receipt model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];
@@ -518,7 +518,7 @@ Visit the Azure samples repository on GitHub and view the [receipt model output]
 ## Use the ID document model
 
 ```javascript
-const { AzureKeyCredential, DocumentIntelligence } = require("@azure/ai-document-intelligence");
+const { AzureKeyCredential, DocumentIntelligence } = require("@azure-rest/ai-document-intelligence");
 
 //use your `key` and `endpoint` environment variables
 const key = process.env['DI_KEY'];

articles/ai-services/openai/reference.md

@@ -1026,7 +1026,7 @@ curl -X POST https://{your-resource-name}.openai.azure.com/openai/deployments/{d
   -d '{
     "prompt": "An avocado chair",
     "size": "1024x1024",
-    "n": 3,
+    "n": 1,
     "quality": "hd", 
     "style": "vivid"
   }'

articles/aks/workload-identity-deploy-cluster.md

@@ -27,6 +27,9 @@ This article assumes you have a basic understanding of Kubernetes concepts. For
 
 - If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the [az account][az-account] command.
 
+> [!NOTE]
+> Instead of configuring all steps manually, there is another implementation called _Service Connector_ which will help you configure some steps automatically and achieve the same outcome. See also: [Tutorial: Connect to Azure storage account in Azure Kubernetes Service (AKS) with Service Connector using workload identity][tutorial-python-aks-storage-workload-identity].
+
 ## Export environment variables
 
 To help simplify steps to configure the identities required, the steps below define
@@ -268,6 +271,7 @@ In this article, you deployed a Kubernetes cluster and configured it to use a wo
 [az-keyvault-list]: /cli/azure/keyvault#az-keyvault-list
 [aks-identity-concepts]: concepts-identity.md
 [az-account]: /cli/azure/account
+[tutorial-python-aks-storage-workload-identity]: ../service-connector/tutorial-python-aks-storage-workload-identity.md
 [az-aks-create]: /cli/azure/aks#az-aks-create
 [az aks update]: /cli/azure/aks#az-aks-update
 [aks-two-resource-groups]: faq.md#why-are-two-resource-groups-created-with-aks

articles/aks/workload-identity-overview.md

@@ -20,6 +20,9 @@ Microsoft Entra Workload ID works especially well with the [Azure Identity clien
 
 This article helps you understand this new authentication feature, and reviews the options available to plan your project strategy and potential migration from Microsoft Entra pod-managed identity.
 
+> [!NOTE]
+> Instead of configuring all steps manually, there is another implementation called _Service Connector_ which will help you configure some steps automatically. See also: [What is Service Connector?][service-connector-overview]
+
 ## Dependencies
 
 - AKS supports Microsoft Entra Workload ID on version 1.22 and higher.
@@ -303,6 +306,7 @@ The following table summarizes our migration or deployment recommendations for w
 [virtual-kubelet]: https://virtual-kubelet.io/docs/
 
 <!-- INTERNAL LINKS -->
+[service-connector-overview]: ../service-connector/overview.md
 [use-azure-ad-pod-identity]: use-azure-ad-pod-identity.md
 [azure-ad-workload-identity]: ../active-directory/develop/workload-identities-overview.md
 [microsoft-authentication-library]: ../active-directory/develop/msal-overview.md

articles/app-service/reference-app-settings.md

@@ -420,7 +420,7 @@ The following are 'fake' environment variables that don't exist if you enumerate
 | `WEBSITE_LOCAL_CACHE_READWRITE_OPTION` | Read-write options of the local cache. Available options are: <br/>- `ReadOnly`: Cache is read-only.<br/>- `WriteButDiscardChanges`: Allow writes to local cache but discard changes made locally. |
 | `WEBSITE_LOCAL_CACHE_SIZEINMB` | Size of the local cache in MB. Default is `1000` (1 GB). |
 | `WEBSITE_LOCALCACHE_READY` | Read-only flag indicating if the app using local cache. |
-| `WEBSITE_DYNAMIC_CACHE` | Due to network file shared nature to allow access for multiple instances, the dynamic cache improves performance by caching the recently accessed files locally on an instance. Cache is invalidated when file is modified. The cache location is `%SYSTEMDRIVE%\local\DynamicCache` (same `%SYSTEMDRIVE%\local` quota is applied). By default, full content caching is enabled (set to `1`), which includes both file content and directory/file metadata (timestamps, size, directory content). To conserve local disk use, set to `2` to cache only directory/file metadata (timestamps, size, directory content). To turn off caching, set to `0`. |
+| `WEBSITE_DYNAMIC_CACHE` | Due to network file shared nature to allow access for multiple instances, the dynamic cache improves performance by caching the recently accessed files locally on an instance. Cache is invalidated when file is modified. The cache location is `%SYSTEMDRIVE%\local\DynamicCache` (same `%SYSTEMDRIVE%\local` quota is applied). To enable full content caching, set to `1`, which includes both file content and directory/file metadata (timestamps, size, directory content). To conserve local disk use, set to `2` to cache only directory/file metadata (timestamps, size, directory content). To turn off caching, set to `0`. For Windows apps and for [Linux apps created with the WordPress template](quickstart-wordpress.md), the default is `1`. For all other Linux apps, the default is `0`. |
 | `WEBSITE_READONLY_APP` | When using dynamic cache, you can disable write access to the app root (`D:\home\site\wwwroot` or `/home/site/wwwroot`)  by setting this variable to `1`. Except for the `App_Data` directory, no exclusive locks are allowed, so that deployments don't get blocked by locked files. |
 
 <!-- 

articles/azure-arc/servers/private-link-security.md

@@ -282,10 +282,7 @@ For Azure Arc-enabled servers that were set up prior to your private link scope,
 
 1. Select the servers in the list that you want to associate with the Private Link Scope, and then select **Select** to save your changes.
 
-    > [!NOTE]
-    > Only Azure Arc-enabled servers in the same subscription and region as your Private Link Scope is shown.
-
-    :::image type="content" source="./media/private-link-security/select-servers-private-link-scope.png" lightbox="./media/private-link-security/select-servers-private-link-scope.png" alt-text="Selecting Azure Arc resources" border="true":::
+  :::image type="content" source="./media/private-link-security/select-servers-private-link-scope.png" lightbox="./media/private-link-security/select-servers-private-link-scope.png" alt-text="Selecting Azure Arc resources" border="true":::
 
 It might take up to 15 minutes for the Private Link Scope to accept connections from the recently associated server(s).
 

articles/iot-operations/manage-mqtt-connectivity/howto-configure-authentication.md

@@ -56,7 +56,7 @@ BrokerListener and BrokerAuthentication are separate resources, but they're link
 
 The order of authentication methods in the array determines how Azure IoT MQ authenticates clients. Azure IoT MQ tries to authenticate the client's credentials using the first specified method and iterates through the array until it finds a match or reaches the end.
 
-For each method, Azure IoT MQ first checks if the client's credentials are *relevant* for that method. For example, SAT authentication requires a username starting with `sat://`, and X.509 authentication requires a client certificate. If the client's credentials are relevant, Azure IoT MQ then verifies if they're valid. For more information, see the [Configure authentication method](#configure-authentication-method) section.
+For each method, Azure IoT MQ first checks if the client's credentials are *relevant* for that method. For example, SAT authentication requires a username starting with `$sat`, and X.509 authentication requires a client certificate. If the client's credentials are relevant, Azure IoT MQ then verifies if they're valid. For more information, see the [Configure authentication method](#configure-authentication-method) section.
 
 For custom authentication, Azure IoT MQ treats failure to communicate with the custom authentication server as *credentials not relevant*. This behavior lets Azure IoT MQ fall back to other methods if the custom server is unreachable.
 
@@ -94,7 +94,7 @@ The earlier example specifies custom, SAT, and [username-password authentication
 
 1. If the custom authentication server responds with `Pass` or `Fail` result, the authentication flow ends. However, if the custom authentication server isn't available, then Azure IoT MQ falls back to the remaining specified methods, with SAT being next.
 
-1. Azure IoT MQ tries to authenticate the credentials as SAT credentials. If the MQTT username starts with `sat://`, Azure IoT MQ evaluates the MQTT password as a SAT. Otherwise, the broker falls back to username-password and check if the provided MQTT username and password are valid.
+1. Azure IoT MQ tries to authenticate the credentials as SAT credentials. If the MQTT username starts with `$sat`, Azure IoT MQ evaluates the MQTT password as a SAT. Otherwise, the broker falls back to username-password and check if the provided MQTT username and password are valid.
 
 If the custom authentication server is unavailable and all subsequent methods determined that the provided credentials aren't relevant, then the broker denies the client connection.
 

articles/notification-hubs/notification-hubs-diagnostic-logs.md

@@ -103,8 +103,6 @@ Operational logs are disabled by default. To enable logs, do the following:
 
    b. Select one of the following three destinations for your diagnostics logs:  
    - If you select **Send to Log Analytics workspace**, you need to specify which instance of Log Analytics the diagnostics will be sent to.
-     > [!NOTE]
-     > Sending to the Log Analytics workspace is currently not supported.
    - If you select **Archive to a storage account**, you need to configure the storage account where the diagnostics logs will be stored.  
    - If you select **Stream to an event hub**, you need to configure the event hub that you want to stream the diagnostics logs to.
 
@@ -122,4 +120,4 @@ To learn more about configuring diagnostics settings, see:
 * [Overview of Azure diagnostics logs](../azure-monitor/essentials/platform-logs-overview.md).
 
 To learn more about Azure Notification Hubs, see:
-* [What is Azure Notification Hubs?](notification-hubs-push-notification-overview.md)
+* [What is Azure Notification Hubs?](notification-hubs-push-notification-overview.md)

articles/spring-apps/enterprise/whats-new.md

@@ -6,7 +6,7 @@ ms.author: hangwan
 ms.service: spring-apps
 ms.topic: conceptual
 ms.custom: devx-track-java
-ms.date: 10/10/2023
+ms.date: 04/15/2024
 ---
 
 # What's new in Azure Spring Apps?
@@ -18,6 +18,20 @@ Azure Spring Apps is improved on an ongoing basis. To help you stay up to date w
 
 This article is updated quarterly, so revisit it regularly. You can also visit [Azure updates](https://azure.microsoft.com/updates/?query=azure%20spring), where you can search for updates or browse by category.
 
+## Q1 2024
+
+The following updates are now available in the Enterprise plan:
+
+- **Save up to 47%: Azure Spring Apps Enterprise is now eligible for Azure savings plan**: All Azure Spring Apps regions under the Enterprise plan are eligible for substantial cost savings – 20% for one year and 47% for three years – when you commit to the Azure savings plan. For more information, see [Azure Spring Apps Enterprise is now eligible for Azure savings plan for compute](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-spring-apps-enterprise-is-now-eligible-for-azure-savings/ba-p/4021532).
+
+- **Azure CLI supports log streaming for Spring Cloud Gateway**: This feature enables you to fetch the Spring Cloud Gateway log in real time for diagnosis purposes. For more information, see the [Use real-time log streaming](how-to-troubleshoot-enterprise-spring-cloud-gateway.md#use-real-time-log-streaming) section of [Troubleshoot VMware Spring Cloud Gateway](how-to-troubleshoot-enterprise-spring-cloud-gateway.md).
+
+- **Azure CLI supports log streaming for Application Configuration Service**: The feature enables you to retrieve the Application Configuration Service log using the Azure CLI, making it possible to detect any configuration updates. For more information, see the [Use real-time log streaming](how-to-enterprise-application-configuration-service.md#use-real-time-log-streaming) section of [Use Application Configuration Service for Tanzu](how-to-enterprise-application-configuration-service.md).
+
+- **Shows buildpack versions**: The latest feature added to buildpacks assists you in comprehending the version used and diagnosing issues associated with the build process.
+
+- **Enhanced troubleshooting of Application Configuration Service**: Now you can directly view the linked `configMap` for your apps to further assist in troubleshooting issues with unrefreshed configurations. You can also export configuration files pulled by the Application Configuration Service from upstream Git repositories to your local environment through the Azure CLI. This process helps you examine the content and use configuration files for local development. For more information, see the [Examine configuration file in ConfigMap](how-to-enterprise-application-configuration-service.md#examine-configuration-file-in-configmap) section of [Use Application Configuration Service for Tanzu](how-to-enterprise-application-configuration-service.md).
+
 ## Q4 2023
 
 The following updates are now available in the Enterprise plan: