Merge pull request #314162 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/private-link/network-security-perimeter-concepts.md

@@ -141,6 +141,9 @@ Network security perimeter is currently available in all Azure public cloud regi
 > [!NOTE]
 > For PaaS resource logs, use **Log Analytics Workspace, Storage or Event Hub** as the log destination associated to the same perimeter as the PaaS resource.
 
+> [!NOTE]
+> Azure Backup is not supported for Storage Accounts enabled with network security perimeter. We recommend not associating a storage account with network security perimeter if you have backups enabled or if you plan to use Azure Backup.
+
 [!INCLUDE [network-security-perimeter-limits](../../includes/network-security-perimeter-limits.md)]
 
 ## Next steps

includes/network-security-perimeter-note-managed-id.md

@@ -11,4 +11,4 @@ ms.custom: include file, ignite-2024
 ---
 
 > [!NOTE]
-> If managed identity is not assigned to the resource which supports it, outbound access to other resources within the same perimeter will be denied. Subscription based inbound rules intended to allow access from this resource will not take effect.  
+> Enabling a Managed Identity (MI) is required to support intra-perimeter communication between resources. While some capabilities for certain resources (for example, Azure SQL's features that use platform‑managed, SQL‑to‑SQL backend communication) may continue to function without an MI, enabling one is strongly recommended to ensure secure access within the same perimeter or across linked perimeters.