Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rs-ps

Author: halkazwini

articles/azure-functions/functions-premium-plan.md

@@ -249,11 +249,12 @@ These are the currently supported maximum scale-out values for a single plan in
 |Canada Central| 100 | 100 |
 |Central India| 100 | 20 |
 |Central US| 100 | 100 |
-|China East 2| 100 | 20 |
-|China North 2| 100 | 20 |
+|China East 2| 20 | 20 |
+|China North 2| 20 | 20 |
+|China North 3| 20 | 20 |
 |East Asia| 100 | 20 |
 |East US | 100 | 100 |
-|East US 2| 100 | 100 |
+|East US 2| 80 | 100 |
 |France Central| 100 | 60 |
 |Germany West Central| 100 | 20 |
 |Israel Central| 100 | 20 |
@@ -278,9 +279,9 @@ These are the currently supported maximum scale-out values for a single plan in
 |UAE North| 100 | 20 |
 |UK South| 100 | 100 |
 |UK West| 100 | 20 |
-|USGov Arizona| 100 | 20 |
-|USGov Texas| 100 | Not Available |
-|USGov Virginia| 100 | 20 |
+|USGov Arizona| 20 | 20 |
+|USGov Texas| 20 | Not Available |
+|USGov Virginia| 80 | 20 |
 |West Central US| 100 | 20 |
 |West Europe| 100 | 100 |
 |West India| 100 | 20 |

articles/azure-functions/functions-scenarios.md

@@ -24,7 +24,7 @@ For example, in a retail solution, a partner system can submit product catalog i
 [ ![Diagram of a file upload process using Azure Functions.](./media/functions-scenarios/process-file-uploads.png) ](./media/functions-scenarios/process-file-uploads-expanded.png#lightbox)
 
 
-The following tutorials use an Event Grid trigger to process files in a blob container:
+The following tutorials use a Blob trigger (Event Grid based) to process files in a blob container:
 
 ::: zone pivot="programming-language-csharp" 
 
@@ -50,6 +50,7 @@ public static async Task Run([BlobTrigger("catalog-uploads/{name}", Source = Blo
 }
 ```
 
++ [Event-based Blob storage triggered function that converts PDF documents to text at scale](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/tree/main/E2E/BLOB-PDF)
 + [Upload and analyze a file with Azure Functions and Blob Storage](../storage/blobs/blob-upload-function-trigger.md?tabs=dotnet)
 + [Automate resizing uploaded images using Event Grid](../event-grid/resize-images-on-storage-blob-upload-event.md?tabs=dotnet)
 + [Trigger Azure Functions on blob containers using an event subscription](functions-event-grid-blob-trigger.md?pivots=programming-language-csharp)

articles/azure-netapp-files/backup-requirements-considerations.md

@@ -38,7 +38,7 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
 
 * In a [cross-region replication](cross-region-replication-introduction.md) (CRR) or [cross-zone replication](cross-zone-replication-introduction.md) (CZR) setting, Azure NetApp Files backup can be configured on a source volume. 
 
-    Backups on a destination volume are only supported for manually created snapshots. To take backups of a destination volume, create a snapshot on the source volume then wait for the snapshot to be replicated to the destination volume. From the destination volume, you can select the snapshot for backup, where you can select this snapshot for backup. Scheduled backups on a destination volume aren't supported.
+    Backups on a destination volume are only supported for manually created snapshots. To take backups of a destination volume, create a snapshot on the source volume then wait for the snapshot to be replicated to the destination volume. From the destination volume, you select the snapshot for backup. Scheduled backups on a destination volume aren't supported.
 
 * See [Restore a backup to a new volume](backup-restore-new-volume.md) for additional considerations related to restoring backups.
 

articles/azure-resource-manager/management/tag-resources.md

@@ -79,7 +79,7 @@ The following limitations apply to tags:
 * Tag names can't contain these characters: `<`, `>`, `%`, `&`, `\`, `?`, `/`
 
    > [!NOTE]
-   > * Azure Domain Name System (DNS) zones don't support the use of spaces in the tag or a tag that starts with a number. Azure DNS tag names don't support special and unicode characters. The value can contain all characters.
+   > * Azure Domain Name System (DNS) zones don't support the use of spaces or parentheses in the tag or a tag that starts with a number. Azure DNS tag names don't support special and unicode characters. The value can contain all characters.
    >
    > * Traffic Manager doesn't support the use of spaces, `#` or `:` in the tag name. The tag name can't start with a number.
    >

articles/communication-services/concepts/analytics/logs/email-logs.md

@@ -94,7 +94,10 @@ Communication Services offers the following types of logs that you can enable:
 
 ## Email Status Update operational logs
 
-*Email status update operational logs* provide in-depth insights into message and recipient level delivery status updates on your sendmail API requests. These logs offer message-specific details, such as the time of delivery, as well as recipient-level details, such as email addresses and delivery status updates. By tracking these logs, you can ensure full visibility into your email delivery process, quickly identifying any issues that may arise and taking corrective action as necessary.
+*Email status update operational logs* provide in-depth insights into message-level and recipient-level delivery status updates on your sendmail API requests.
+- Message-level status updates provide the status of the long-running email send operation (similar to the status updates you receive through calling our GET APIs). These are marked by the absence of `RecipientId` property because these updates are for the entire message and not applicable to a specific recipient in that message request. `DeliveryStatus` property contains the message-level delivery status. Possible values for `DeliveryStatus` for this type of event are `Dropped`, `OutForDelivery`, and `Queued`.
+- Recipient-level status updates provide the status of email delivery for each individual recipient to whom the email was sent in a single message. These contain a `RecipientId` property with the recipient's email address. Recipient-level delivery status is provided in the `DeliveryStatus` property. Possible values for `DeliveryStatus` for this type of event are `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, and `Bounced`.
+By tracking these logs, you can ensure full visibility into your email delivery process, quickly identifying any issues that may arise and taking corrective action as necessary.
 
 | Property | Description |
 | -------- | ---------------|
@@ -104,8 +107,8 @@ Communication Services offers the following types of logs that you can enable:
 | `OperationVersion` | The `api-version` associated with the operation, if the `operationName` was performed using an API. If there's no API that corresponds to this operation, the version represents the version of that operation in case the properties associated with the operation change in the future. |
 | `Category` | The log category of the event. The category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the properties blob of an event are the same within a particular log category and resource type. |
 | `CorrelationID` | The ID for correlated events. Can be used to identify correlated events between multiple tables. For all Email operational logs, the CorrelationId is mapped to the MessageId, which is returned from a successful SendMail request. |
-| `RecipientId` | The email address for the targeted recipient. If this is a message-level event, the property will be empty. |
-| `DeliveryStatus` | The terminal status of the message. |
+| `RecipientId` | The email address for the targeted recipient. It is only present for recipient-level events. If this is a message-level event, the property will be empty. |
+| `DeliveryStatus` | The terminal status of the message. Possible valuse for message-level event are: `Dropped`, `OutForDelivery`, `Queued`. Possible valuse for a recipient-level event are: `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, `Bounced`. |
 | `SmtpStatusCode` | SMTP status code returned from the recipient email server in response to a send mail request.
 | `EnhancedSmtpStatusCode` | Enhanced SMTP status code returned from the recipient email server.
 | `SenderDomain` | The domain portion of the SenderAddress used in sending emails.
@@ -160,4 +163,4 @@ Communication Services offers the following types of logs that you can enable:
   "EngagementContext":"https://www.contoso.com/support?id=12345", 
   "UserAgent":"Mozilla/5.0"
 }
-```
+```

articles/hdinsight/azure-monitor-agent.md

@@ -185,7 +185,7 @@ We also improved the out-of-box dashboards both at the cluster-level. There's a
 
 ## Release and support timeline
 
-* Classic Azure Monitoring integration isn't unavailable after October 15, 2021. You can't enable classic Azure Monitoring integration after that date. 
+* Classic Azure Monitoring integration isn't available after October 15, 2021. You can't enable classic Azure Monitoring integration after that date. 
 
 * Classic Azure Monitoring integration ingestion will not be working after August 31, 2024.