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

Author: roygara

articles/application-gateway/understanding-pricing.md

@@ -48,6 +48,7 @@ The parameter with the highest utilization among these three parameters is used
 
 #### Capacity Unit related to Instance Count
 <h4 id="instance-count"></h4>
+
 You can also pre-provision resources by specifying the **Instance Count**. Each instance guarantees a minimum of 10 capacity units in terms of processing capability. The same instance could potentially support more than 10 capacity units for different traffic patterns depending upon the capacity unit parameters.
 
 Manually defined scale and limits set for autoscaling (minimum or maximum) are set in terms of instance count. The manually set scale for instance count and the minimum instance count in autoscale config reserves 10 capacity units/instance. These reserved capacity units are billed as long as the application gateway is active regardless of the actual resource consumption. If actual consumption crosses the 10 capacity units/instance threshold, additional capacity units are billed under the variable component.

articles/azure-monitor/alerts/action-groups.md

@@ -351,7 +351,7 @@ When an email address is rate limited, a notification is sent to communicate tha
 When you use Azure Resource Manager for email notifications, you can send email to the members of a subscription's role. Email is sent to Microsoft Entra ID **user** or **group** members of the role. This includes support for roles assigned through Azure Lighthouse.
 
 > [!NOTE]
-> Action Groups only supports emailing the following roles: Owner, Contirbutor, Reader, Monitoring Contributor, Monitoring Reader.
+> Action Groups only supports emailing the following roles: Owner, Contributor, Reader, Monitoring Contributor, Monitoring Reader.
 
 If your primary email doesn't receive notifications, configure the email address for the Email Azure Resource Manager role:
 

articles/azure-monitor/containers/media/prometheus-remote-write-managed-identity/data-collection-rule-add-role-assignment.png

@@ -184,6 +184,8 @@ Malware Scanning doesn't automatically block access or change permissions to the
 
 - Unsupported storage accounts: Legacy v1 storage accounts aren't supported by malware scanning.
 - Unsupported service: Azure Files isn't supported by malware scanning.
+- Unsupported client: Blobs uploaded with Network File System (NFS) 3.0 protocol will not be scanned for malware upon upload.
+
 - Unsupported regions: Jio India West, Korea South, South Africa West.
 - Regions that are supported by Defender for Storage but not by malware scanning. Learn more about [availability for Defender for Storage.](defender-for-storage-introduction.md)
 

articles/defender-for-cloud/defender-for-storage-malware-scan.md

@@ -55,7 +55,7 @@ Azure API for FHIR was our initial generally available product and is being reti
 |**Autoscaling**|Supported on request and incurs charge|[Autoscaling](fhir-service-autoscale.md) enabled by default at no extra charge|
 |**Search parameters**|Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported  <br> • Sorting supported by first name, last name, birthdate and clinical date|Bundle type supported: Batch and transaction  <br> • [Selectable search parameters](selectable-search-parameters.md)  <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields|
 |**Events**|Not Supported|Supported|
-|**Convert-data**|Supports enabling "Allow trusted services" in Account container registry| There is a known issue -"Enabling "Allow trusted services" in the Account Container Registry may result in access issues when attempting to use the container registry from the FHIR service."|
+|**Convert-data**|Supports enabling "Allow trusted services" in Account container registry| There is a known issue -Enabling private link with Azure Container Registry may result in access issues when attempting to use the container registry from the FHIR service.|
 |**Business continuity**|Supported:<br> • Cross region DR (disaster recovery)  <br>|Supported: <br> • PITR (point in time recovery) <br> • Availability zone support|
 
 By default each Azure Health Data Services, FHIR instance is limited to storage capacity of 4TB.

articles/healthcare-apis/fhir/fhir-faq.md

@@ -74,9 +74,9 @@ In this section, you create a
 
 7. Select **IPv4** or **IPv6** for **IP version**.
 
-8. In **Public IP address**, select **Create new**. Enter **myPublicIP-cr** in **Name**.  Select **OK**.
+8. In **Public IP address**, select **Create new**. Enter **myPublicIP-cr** in **Name**.  Select **Save** for the Add Public IP Address Dialog.
 
-9. Select **Add**.
+9. Select **Save**.
 
 10. Select **Next: Backend pools** at the bottom of the page.