Merge pull request #222346 from MicrosoftDocs/main

12/23/2022 PM Publish

Author: Taojunshen

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -100,8 +100,13 @@ To take advantage of geographical distribution of your system, you should have b
     </policies>
     ```
 
-> [!TIP]
-> You may also front your backend services with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/), direct the API calls to the Traffic Manager, and let it resolve the routing automatically.
+### Use Traffic Manager for routing to regional backends
+
+You may also front your backend services with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/), direct the API calls to the Traffic Manager, and let it resolve the routing automatically. 
+
+* For traffic distribution and failover, we recommend using Traffic Manager with the [**Geographic**](../traffic-manager/traffic-manager-routing-methods.md#geographic-traffic-routing-method) routing method. We don't recommend using Traffic Manager with the Weighted routing method with API Management backends.
+
+* For traffic control during maintenance operations, we recommend using the Priority routing method.
 
 ## <a name="custom-routing"> </a>Use custom routing to API Management regional gateways
 

articles/azure-monitor/faq.yml

@@ -737,7 +737,7 @@ sections:
           
           ### Querying the telemetry
           
-          Use the [REST API](https://dev.applicationinsights.io/) to run [Analytics](./logs/log-query-overview.md) queries.
+          Use the [REST API](/rest/api/application-insights/) to run [Analytics](./logs/log-query-overview.md) queries.
           
       - question: |
           How can I set an alert on an event?

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 12/23/2022
 ms.author: ramakk
 ms.custom: references_regions
 ---
@@ -55,6 +55,7 @@ Azure NetApp Files Standard network features are supported for the following reg
 *	North Central US
 *   North Europe
 *   Norway East
+*   South Africa North
 *	South Central US
 *   South India 
 *   Southeast Asia

articles/cognitive-services/Translator/reference/v3-0-break-sentence.md

@@ -9,7 +9,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: translator-text
 ms.topic: reference
-ms.date: 08/06/2020
+ms.date: 12/23/2022
 ms.author: lajanuar
 ---
 
@@ -32,8 +32,8 @@ Request parameters passed on the query string are:
 | Query Parameter | Description |
 | -------| ----------- |
 | api-version <img width=200/>   | **Required query parameter**.<br/>Version of the API requested by the client. Value must be `3.0`. |
-| language | **Optional query parameter**.<br/>Language tag identifying the language of the input text. If a code is not specified, automatic language detection will be applied. |
-| script    | **Optional query parameter**.<br/>Script tag identifying the script used by the input text. If a script is not specified, the default script of the language will be assumed.  | 
+| language | **Optional query parameter**.<br/>Language tag identifying the language of the input text. If a code isn't specified, automatic language detection will be applied. |
+| script    | **Optional query parameter**.<br/>Script tag identifying the script used by the input text. If a script isn't specified, the default script of the language will be assumed.  | 
 
 Request headers include:
 
@@ -42,7 +42,7 @@ Request headers include:
 | Authentication header(s) <img width=200/>  | **Required request header**.<br/>See <a href="/azure/cognitive-services/translator/reference/v3-0-reference#authentication">available options for authentication</a>. |
 | Content-Type | **Required request header**.<br/>Specifies the content type of the payload. Possible values are: `application/json`. |
 | Content-Length    | **Required request header**.<br/>The length of the request body.  | 
-| X-ClientTraceId   | **Optional**.<br/>A client-generated GUID to uniquely identify the request. Note that you can omit this header if you include the trace ID in the query string using a query parameter named `ClientTraceId`.  | 
+| X-ClientTraceId   | **Optional**.<br/>A client-generated GUID to uniquely identify the request. You can omit this header if you include the trace ID in the query string using a query parameter named `ClientTraceId`.  | 
 
 ## Request body
 
@@ -57,35 +57,39 @@ The body of the request is a JSON array. Each array element is a JSON object wit
 The following limitations apply:
 
 * The array can have at most 100 elements.
-* The text value of an array element cannot exceed 50,000 characters including spaces.
-* The entire text included in the request cannot exceed 50,000 characters including spaces.
+* The text value of an array element can't exceed 50,000 characters including spaces.
+* The entire text included in the request can't exceed 50,000 characters including spaces.
 * If the `language` query parameter is specified, then all array elements must be in the same language. Otherwise, language auto-detection is applied to each array element independently.
 
 ## Response body
 
 A successful response is a JSON array with one result for each string in the input array. A result object includes the following properties:
 
-  * `sentLen`: An array of integers representing the lengths of the sentences in the text element. The length of the array is the number of sentences, and the values are the length of each sentence. 
+* `sentLen`: An array of integers representing the lengths of the sentences in the text element. The length of the array is the number of sentences, and the values are the length of each sentence. 
 
-  * `detectedLanguage`: An object describing the detected language through the following properties:
+* `detectedLanguage`: An object describing the detected language through the following properties:
 
-     * `language`: Code of the detected language.
+  * `language`: Code of the detected language.
 
-     * `score`: A float value indicating the confidence in the result. The score is between zero and one and a low score indicates a low confidence.
-     
-    Note that the `detectedLanguage` property is only present in the result object when language auto-detection is requested.
+  * `score`: A float value indicating the confidence in the result. The score is between zero and one and a low score indicates a low confidence.
+
+The `detectedLanguage` property is only present in the result object when language auto-detection is requested.
 
 An example JSON response is:
 
 ```json
 [
-  {
-    "sentLen": [ 13, 11, 22 ]
-    "detectedLanguage": {
-      "language": "en",
-      "score": 401
-    },
-  }
+    {
+        "detectedLanguage": {
+            "language": "en",
+            "score": 1.0
+        },
+        "sentLen": [
+            13,
+            11,
+            22
+        ]
+    }
 ]
 ```
 
@@ -96,7 +100,7 @@ An example JSON response is:
   <th>Description</th>
   <tr>
     <td>X-RequestId</td>
-    <td>Value generated by the service to identify the request. It is used for troubleshooting purposes.</td>
+    <td>Value generated by the service to identify the request. It's used for troubleshooting purposes.</td>
   </tr>
 </table> 
 
@@ -117,11 +121,11 @@ The following are the possible HTTP status codes that a request returns.
   </tr>
   <tr>
     <td>401</td>
-    <td>The request could not be authenticated. Check that credentials are specified and valid.</td>
+    <td>The request couldn't be authenticated. Check that credentials are specified and valid.</td>
   </tr>
   <tr>
     <td>403</td>
-    <td>The request is not authorized. Check the details error message. This often indicates that all free translations provided with a trial subscription have been used up.</td>
+    <td>The request isn't authorized. Check the details error message. This response code often indicates that all free translations provided with a trial subscription have been used up.</td>
   </tr>
   <tr>
     <td>429</td>
@@ -145,4 +149,4 @@ The following example shows how to obtain sentence boundaries for a single sente
 
 ```curl
 curl -X POST "https://api.cognitive.microsofttranslator.com/breaksentence?api-version=3.0" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json" -d "[{'Text':'How are you? I am fine. What did you do today?'}]"
-```
+```

articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md

@@ -138,7 +138,6 @@ Here are the important steps from the code:
 In the code sample below, replace the `<CONNECTION_STRING>` and `<HUB_NAME>` placeholder values for the `EventHubProducerClient` parameters.
 
 ```csharp
-using Azure.Identity;
 using Azure.Messaging.EventHubs;
 using Azure.Messaging.EventHubs.Producer;
 using System.Text;

articles/governance/blueprints/index.yml

@@ -106,6 +106,6 @@ landingContent:
           - text: Azure PowerShell
             url: /powershell/module/az.blueprint/#blueprint
           - text: Azure SDK for .NET
-            url: /dotnet/api/overview/azure/blueprints/management
+            url: /dotnet/api/overview/azure/blueprint/management/management-blueprint
           - text: REST
             url: /rest/api/blueprints/

articles/governance/management-groups/index.yml

@@ -66,7 +66,7 @@ landingContent:
           - text: Azure PowerShell
             url: /powershell/module/az.resources/#resources
           - text: Azure SDK for .NET
-            url: /dotnet/api/overview/azure/managementgroups
+            url: /dotnet/api/overview/azure/management-groups
           - text: Azure SDK for Go
             url: https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/services/preview/resources/mgmt/2018-03-01-preview/managementgroups
           - text: Azure SDK for JavaScript
@@ -76,4 +76,4 @@ landingContent:
           - text: REST
             url: /rest/api/managementgroups
           - text: Resource Manager templates
-            url: /azure/templates/microsoft.management/managementgroups
+            url: /azure/templates/microsoft.management/managementgroups

articles/marketplace/customer-dashboard.md

@@ -4,10 +4,10 @@ description: Learn how to access information about your customers, including gro
 ms.service: marketplace 
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: article
-author: smannepalle
-ms.author: smannepalle
+author: saurabhsharmaa
+ms.author: saurasharma
 ms.reviewer: sroy
-ms.date: 05/05/2022
+ms.date: 12/23/2022
 ---
 
 # Customers dashboard in commercial marketplace analytics
@@ -99,7 +99,7 @@ These filters are applied at the Customers page level. Select multiple filters t
 The page has dashboard-level filters for the following:
 
 - Sales Channel
-- Marketplace Subscription Id
+- Marketplace Subscription ID
 - Customer Id
 - Customer Name
 - Customer Company Name
@@ -142,14 +142,14 @@ This chart has tabs for Orders, Normalized usage, and Raw usage. Select **Orders
 ![Screenshot showing the Orders tab on the Insights screen of the Customers dashboard.](./media/customer-dashboard/customers-by-orders-usage.png)
 
 - The Leader board presents details of the customers ranked by order count. After selecting a customer, the customer details are presented in the adjoining “Details”, “Orders by SKUs” and “SKUs by Seats” sections.
-- The Customer profile details are displayed in this space when publishers are signed in with an owner role. If publishers are signed in with a contributor role, the details in this section will not be available.
+- The Customer profile details are displayed in this space when publishers are signed in with an owner role. If publishers are signed in with a contributor role, the details in this section won't be available.
 - The **Orders by SKUs** donut chart displays the breakdown of orders purchased for plans. The top five plans with the highest order count are displayed, while the rest of the orders are grouped under **Rest all**.
 - The **SKUs by Seats** donut chart displays the breakdown of seats ordered for plans. The top five plans with the highest seats are displayed, while the rest of the orders are grouped under **Rest All**.
 
 Select **Normalized usage** or **Raw usage** for those views.
 
 - The Leader board presents details of the customers ranked by usage hours count. After selecting a customer, the details of the customer are presented in the adjoining “Details”, “Normalized Usage by offers” and “Normalized Usage by virtual machine (VM) Size(s)” section.
-- The Customer profile details are displayed in this space when publishers are logged in with an owner role. If publishers are logged in with a contributor role, the details in this section will not be available.
+- The Customer profile details are displayed in this space when publishers are logged in with an owner role. If publishers are logged in with a contributor role, the details in this section won't be available.
 - The **Normalized usage by Offers** donut chart displays the breakdown of usage consumed by the offers. The top five plans with the highest usage count are displayed, while the rest of the offers are grouped under **Rest All**.
 - The **Normalized usage by VM Size(s)** donut chart displays the breakdown of usage consumed by different VM Size(s). The top five VM Sizes with the highest normalized usage are displayed, while the rest of the usage is grouped under **Rest All**.
 
@@ -195,11 +195,11 @@ The **Customer details** table displays a numbered list of the top 1,000 custome
 
 ![Screenshot showing the Customer Details table on the Insights screen of the Customers dashboard.](./media/customer-dashboard/customer-details-table.png)
 
-- Customer personal information will only be available if the customer has provided consent. You can only view this information if you have signed in with an owner role level of permissions.
+- Customer personal information will only be available if the customer has provided consent. You can only view this information if you've signed in with an owner role level of permissions.
 - Each column in the grid is sortable.
 - The data can be extracted to a .CSV or .TSV file if the count of the records is less than 1,000.
 - If records number is more than 1,000, exported data will be asynchronously placed in a downloads page for the next 30 days.
-- Apply filters to the table to display only the data you are interested in. Filter data by Company name, Customer ID, Marketplace Subscription ID, Azure License Type, Date Acquired, Date Lost, Customer Email, Customer Country/Region/State/City/Zip, Customer Language, and so on.
+- Apply filters to the table to display only the data you're interested in. Filter data by Company name, Customer ID, Marketplace Subscription ID, Azure License Type, Date Acquired, Date Lost, Customer Email, Customer Country/Region/State/City/Zip, Customer Language, and so on.
 - When an offer is purchased by a protected customer, information in **Customer Detailed Data** will be masked (************).
 - Customer dimension details such as Company Name, Customer Name, and Customer Email are at an organization ID level, not at Azure Marketplace or Microsoft AppSource transaction level.
 
@@ -209,7 +209,7 @@ _**Table 1: Dictionary of data terms**_
 
 | Column name in<br>user interface | Attribute name | Definition | Column name in programmatic<br>access reports |
 | ------------ | ------------- | ------------- | ------------- |
-| Marketplace Subscription ID | Marketplace Subscription ID | The unique identifier associated with the Azure subscription the customer used to purchase your commercial marketplace offer. For infrastructure offers, this is the customer's Azure subscription GUID. For SaaS offers, this is shown as zeros since SaaS purchases do not require an Azure subscription. | MarketplaceSubscriptionId |
+| Marketplace Subscription ID | Marketplace Subscription ID | The unique identifier associated with the Azure subscription the customer used to purchase your commercial marketplace offer. For infrastructure offers, this is the customer's Azure subscription GUID. For SaaS offers, this is shown as zeros since SaaS purchases don't require an Azure subscription. | MarketplaceSubscriptionId |
 | DateAcquired | Date Acquired | The first date the customer purchased any offer you published. | DateAcquired |
 | DateLost | Date Lost | The last date the customer canceled the last of all previously purchased offers. | DateLost |
 | Provider Name | Provider Name | The name of the provider involved in the relationship between Microsoft and the customer. If the customer is an Enterprise through Reseller, this will be the reseller. If a Cloud Solution Provider (CSP) is involved, this will be the CSP. | ProviderName |
@@ -223,7 +223,7 @@ _**Table 1: Dictionary of data terms**_
 | CustomerCommunicationCulture | Customer Communication Language | The language preferred by the customer for communication. | CustomerCommunicationCulture |
 | CustomerCountryRegion | Customer Country/Region | The country/region name provided by the customer. Country/region could be different than the country/region in a customer's Azure subscription. | CustomerCountryRegion |
 | AzureLicenseType | Azure License Type | The type of licensing agreement used by customers to purchase Azure. Also known as the _channel_. The possible values are:<br>- Cloud Solution Provider<br>- Enterprise<br>- Enterprise through Reseller<br>- Pay as You Go | AzureLicenseType |
-| PromotionalCustomers | Is Promotional Contact Opt In | The value will let you know if the customer proactively opted in for promotional contact from publishers. At this time, we are not presenting the option to customers, so we have indicated "No" across the board. After this feature is deployed, we will start updating accordingly. | PromotionalCustomers |
+| PromotionalCustomers | Is Promotional Contact Opt In | The value will let you know if the customer proactively opted in for promotional contact from publishers. At this time, we aren't presenting the option to customers, so we've indicated "No" across the board. After this feature is deployed, we'll start updating accordingly. | PromotionalCustomers |
 | CustomerState | Customer State | The state of residence provided by the customer. State could be different than the state provided in a customer's Azure subscription. | CustomerState |
 | CommerceRootCustomer | Commerce Root Customer | One Billing Account ID can be associated with multiple Customer IDs.<br>One combination of a Billing Account ID and a Customer ID can be associated with multiple commercial marketplace subscriptions.<br>The Commerce Root Customer signifies the name of the subscription’s customer. | CommerceRootCustomer |
 | Customer ID | Customer ID | The unique identifier assigned to a customer. A customer may have zero or more Azure Marketplace subscriptions. | CustomerId |
@@ -233,6 +233,14 @@ _**Table 1: Dictionary of data terms**_
 | PlanID | PlanID | The display name of the plan entered when the offer was created in Partner Center | PlanID |
 | SKU | SKU | The plan associated with the offer | SKU |
 | N/A | lastModifiedAt | The latest timestamp for customer purchases. Use this field, via programmatic API access, to pull the latest snapshot of all customer purchase transactions since a specific date | lastModifiedAt |
+|	N/A	|	AddressLine1	|	The Address Line 1 section of customer’s street address	|	AddressLine1	|
+|	N/A	|	Billing Id  	|	The Billing Id of the enterprise customer	|	Billing Id  	|
+|	N/A	|	Private Offer Id  	|	The Id to identify a private marketplace offer	|	Private Offer Id  	|
+|	N/A	|	Private Offer Name  	|	The name provided during private offer creation	|	Private Offer Name  	|
+|	N/A	|	Purchaser Email  	|	Email of the entity purchasing or provisioning an offer. This could be same or different than the email of “bill-to” entity	|	Purchaser Email  	|
+|	N/A	|	ReferenceId	|	A unique identifier to indicate provisioned instances or purchased offers by the customer. This key can be used to link with Orders and Usage report  	|	ReferenceId	|
+|	Offer Id  	|	Offer Id  	|	The Id to identify a marketplace offer	|	OfferId  	|
+|	Is Private Plan  	|	Is Private Plan  	|	Indicates whether a marketplace offer is private plan. <li> 0 value indicates false </li> <li> 1 value indicates true </li>	|	IsPrivatePlan  	|
 
 ## Next steps