Merge pull request #280459 from MicrosoftDocs/main

Publish to Live Wednesday 4AM PST 7/10

Author: PMEds28

articles/azure-arc/system-center-virtual-machine-manager/support-matrix-for-system-center-virtual-machine-manager.md

@@ -0,0 +1,144 @@
+---
+title: Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
+description: Learn about the support matrix for Arc-enabled System Center Virtual Machine Manager.
+ms.topic: how-to 
+ms.service: azure-arc
+ms.subservice: azure-arc-scvmm
+author: PriskeyJeronika-MS
+ms.author: v-gjeronika
+manager: jsuri
+ms.date: 07/10/2024
+keywords: "VMM, Arc, Azure"
+
+# Customer intent: As a VI admin, I want to understand the support matrix for System Center Virtual Machine Manager.
+---
+
+# Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
+
+This article documents the prerequisites and support requirements for using [Azure Arc-enabled System Center Virtual Machine Manager (SCVMM)](overview.md) to manage your SCVMM managed on-premises VMs through Azure Arc.
+
+To use Arc-enabled SCVMM, you must deploy an Azure Arc Resource Bridge in your SCVMM managed environment. The Resource Bridge provides an ongoing connection between your SCVMM management server and Azure. Once you've connected your SCVMM management server to Azure, components on the Resource Bridge discover your SCVMM management server inventory. You can [enable them in Azure](enable-scvmm-inventory-resources.md) and start performing virtual hardware and guest OS operations on them using Azure Arc.
+
+## System Center Virtual Machine Manager requirements
+
+The following requirements must be met in order to use Arc-enabled SCVMM.
+
+### Supported SCVMM versions
+
+Azure Arc-enabled SCVMM works with VMM 2019 and 2022 versions and supports SCVMM management servers with a maximum of 15,000 VMs.
+
+> [!NOTE]
+> If VMM server is running on Windows Server 2016 machine, ensure that [Open SSH package](https://github.com/PowerShell/Win32-OpenSSH/releases) is installed.
+> If you deploy an older version of appliance (version lesser than 0.2.25), Arc operation fails with the error *Appliance cluster is not deployed with AAD authentication*. To fix this issue, download the latest version of the onboarding script and deploy the Resource Bridge again.
+> Azure Arc Resource Bridge deployment using private link is currently not supported.
+
+| **Requirement** | **Details** |
+| --- | --- |
+| **Azure** | An Azure subscription  <br/><br/> A resource group in the above subscription where you have the *Owner/Contributor* role. |
+| **SCVMM** | You need an SCVMM management server running version 2019 or later.<br/><br/> A private cloud or a host group with a minimum free capacity of 32 GB of RAM, 4 vCPUs with 100 GB of free disk space. <br/><br/> A VM network with internet access, directly or through proxy. Appliance VM will be deployed using this VM network.<br/><br/> Only Static IP allocation is supported and VMM Static IP Pool is required. Follow [these steps](/system-center/vmm/network-pool?view=sc-vmm-2022&preserve-view=true) to create a VMM Static IP Pool and ensure that the Static IP Pool has at least four IP addresses. If your SCVMM server is behind a firewall, all IPs in this IP Pool and the Control Plane IP should be allowed to communicate through WinRM ports. The default WinRM ports are 5985 and 5986. <br/><br/> Dynamic IP allocation using DHCP isn't supported. <br/><br/> A library share with write permission for the SCVMM admin account through which Resource Bridge deployment is going to be performed.  |
+| **SCVMM accounts** | An SCVMM admin account that can perform all administrative actions on all objects that VMM manages. <br/><br/> The user should be part of local administrator account in the SCVMM server. If the SCVMM server is installed in a High Availability configuration, the user should be a part of the local administrator accounts in all the SCVMM cluster nodes. <br/><br/>This will be used for the ongoing operation of Azure Arc-enabled SCVMM and the deployment of the Arc Resource Bridge VM. |
+| **Workstation** | The workstation will be used to run the helper script. Ensure you have [64-bit Azure CLI installed](/cli/azure/install-azure-cli) on the workstation.<br/><br/> When you execute the script from a Linux machine, the deployment takes a bit longer and you might experience performance issues. |
+
+### Resource Bridge networking requirements
+
+The following firewall URL exceptions are required for the Azure Arc Resource Bridge VM:
+
+[!INCLUDE [network-requirements](../resource-bridge/includes/network-requirements.md)]
+
+>[!Note] 
+> To configure SSL proxy and to view the exclusion list for no proxy, see [Additional network requirements](../resource-bridge/network-requirements.md#azure-arc-resource-bridge-network-requirements).
+
+In addition, SCVMM requires the following exception:
+
+| **Service** | **Port** | **URL** | **Direction** | **Notes**|
+| --- | --- | --- | --- | --- |
+| SCVMM Management Server | 443 | URL of the SCVMM management server. | Appliance VM IP and control plane endpoint need outbound connection. | Used by the SCVMM server to communicate with the Appliance VM and the control plane. |
+| WinRM | WinRM Port numbers (Default: 5985 and 5986). | URL of the WinRM service. | IPs in the IP Pool used by the Appliance VM and control plane need connection with the VMM server. | Used by the SCVMM server to communicate with the Appliance VM. |
+
+Generally, connectivity requirements include these principles: 
+
+- All connections are TCP unless otherwise specified. 
+- All HTTP connections use HTTPS and SSL/TLS with officially signed and verifiable certificates. 
+- All connections are outbound unless otherwise specified. 
+
+To use a proxy, verify that the agents and the machine performing the onboarding process meet the network requirements in this article. For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).
+
+### Azure role/permission requirements
+
+The minimum Azure roles required for operations related to Arc-enabled SCVMM are as follows: 
+
+| **Operation** | **Minimum role required** | **Scope** |
+| --- | --- | --- |
+| Onboarding your SCVMM Management Server to Arc | Azure Arc SCVMM Private Clouds Onboarding  | On the subscription or resource group into which you want to onboard |
+| Administering Arc-enabled SCVMM | Azure Arc SCVMM Administrator | On the subscription or resource group where SCVMM management server resource is created  |
+| VM Provisioning | Azure Arc SCVMM Private Cloud User  | On the subscription or resource group that contains the SCVMM cloud, datastore, and virtual network resources, or on the resources themselves |
+| VM Provisioning | Azure Arc SCVMM VM Contributor | On the subscription or resource group where you want to provision VMs |
+| VM Operations | Azure Arc SCVMM VM Contributor | On the subscription or resource group that contains the VM, or on the VM itself |
+
+Any roles with higher permissions on the same scope, such as Owner or Contributor, will also allow you to perform the operations listed above. 
+
+### Azure connected machine agent (Guest Management) requirements
+
+Ensure the following before you install Arc agents at scale for SCVMM VMs:
+
+- The Resource Bridge must be in a running state.
+- The SCVMM management server must be in a connected state.
+- The user account must have permissions listed in Azure Arc-enabled SCVMM Administrator role.
+- All the target machines are:
+     - Powered on and the resource bridge has network connectivity to the host running the VM.
+     - Running a [supported operating system](/azure/azure-arc/servers/prerequisites#supported-operating-systems).
+     - Able to connect through the firewall to communicate over the Internet and [these URLs](/azure/azure-arc/servers/network-requirements?tabs=azure-cloud#urls) aren't blocked.
+
+### Supported SCVMM versions
+
+Azure Arc-enabled SCVMM supports direct installation of Arc agents in VMs managed by:
+
+- SCVMM 2022 UR1 or later versions of SCVMM server or console
+- SCVMM 2019 UR5 or later versions of SCVMM server or console
+
+For VMs managed by other SCVMM versions, [install Arc agents through the script](install-arc-agents-using-script.md).
+
+>[!Important]
+>We recommend maintaining the SCVMM management server and the SCVMM console in the same Long-Term Servicing Channel (LTSC) and Update Rollup (UR) version.
+
+### Supported operating systems
+
+Azure Arc-enabled SCVMM supports direct installation of Arc agents in VMs running Windows Server 2022, 2019, 2016, 2012R2, Windows 10, and Windows 11 operating systems. For other Windows and Linux operating systems, [install Arc agents through the script](install-arc-agents-using-script.md).
+
+### Software requirements
+
+Windows operating systems:
+
+* Microsoft recommends running the latest version, [Windows Management Framework 5.1](https://www.microsoft.com/download/details.aspx?id=54616).
+
+Linux operating systems:
+
+* systemd
+* wget (to download the installation script)
+* openssl
+* gnupg (Debian-based systems, only)
+
+### Networking requirements
+
+The following firewall URL exceptions are required for the Azure Arc agents:
+
+| **URL** | **Description** |
+| --- | --- |
+| `aka.ms` | Used to resolve the download script during installation |
+| `packages.microsoft.com` | Used to download the Linux installation package |
+| `download.microsoft.com` | Used to download the Windows installation package |
+| `login.windows.net` | Microsoft Entra ID |
+| `login.microsoftonline.com` | Microsoft Entra ID |
+| `pas.windows.net` | Microsoft Entra ID |
+| `management.azure.com` | Azure Resource Manager - to create or delete the Arc server resource |
+| `*.his.arc.azure.com` | Metadata and hybrid identity services |
+| `*.guestconfiguration.azure.com` | Extension management and guest configuration services |
+| `guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com` | Notification service for extension and connectivity scenarios |
+| `azgn*.servicebus.windows.net` | Notification service for extension and connectivity scenarios |
+| `*.servicebus.windows.net` | For Windows Admin Center and SSH scenarios |
+| `*.blob.core.windows.net` | Download source for Azure Arc-enabled servers extensions |
+| `dc.services.visualstudio.com` | Agent telemetry |
+
+## Next steps
+
+[Connect your System Center Virtual Machine Manager management server to Azure Arc](quickstart-connect-system-center-virtual-machine-manager-to-arc.md).

articles/azure-arc/system-center-virtual-machine-manager/toc.yml

@@ -22,6 +22,8 @@
   items:
   - name: Deploy
     items:
+    - name: Plan for deployment
+      href: support-matrix-for-system-center-virtual-machine-manager.md
     - name: Enable SCVMM inventory resources in Azure
       href: enable-scvmm-inventory-resources.md
     - name: Enable virtual hardware and VM CRUD capabilities in an SCVMM machine with Arc agent installed

articles/azure-monitor/agents/azure-monitor-agent-send-data-to-event-hubs-and-storage.md

@@ -53,7 +53,7 @@ The Azure Monitor Agent is the new, consolidated telemetry agent for collecting
 
 ## Prerequisites
 
-A [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md) associated with the following resources:
+A managed identity (either system or user) associated with the resources below. We highly recommend using [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md) for better scalability and performance.
 
 - [Storage account](../../storage/common/storage-account-create.md)
 - [Event Hubs namespace and event hub](../../event-hubs/event-hubs-create.md)

articles/azure-monitor/logs/media/logs-data-export/data-export-overview.png

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/07/2023
+ms.date: 07/10/2024
 ms.custom: references_regions
 ms.author: anfdocs
 ---
@@ -71,7 +71,7 @@ This section shows you how to set the network features option when you create a
 
 ## Edit network features option for existing volumes
 
-You can edit the network features option of existing volumes from *Basic* to *Standard* network features. The change you make applies to all volumes in the same *network sibling set* (or *siblings*). Siblings are determined by their network IP address relationship. They share the same NIC for mounting the volume to the client or connecting to the SMB share of the volume. At the creation of a volume, its siblings are determined by a placement algorithm that aims for reusing the IP address where possible. 
+You can edit the network features option of existing volumes from *Basic* to *Standard* network features. The change you make applies to all volumes in the same *network sibling set* (or *siblings*). Siblings are determined by their network IP address relationship. They share the same NIC for mounting the volume to the client or connecting to the remote share of the volume. At the creation of a volume, its siblings are determined by a placement algorithm that aims for reusing the IP address where possible.
 
 >[!IMPORTANT]
 >It's not recommended that you use the edit network features option with Terraform-managed volumes due to risks. You must follow separate instructions if you use Terraform-managed volumes. For more information see, [Update Terraform-managed Azure NetApp Files volume from Basic to Standard](#update-terraform-managed-azure-netapp-files-volume-from-basic-to-standard).

articles/azure-monitor/logs/media/summary-rules/ingestion-flow.png

@@ -57,7 +57,7 @@ If you're affected, we recommend you migrate your Cloud Service or [Cloud Servic
 
 ## Important clarification regarding support 
 
-The announcement of the retirement of Azure Guest OS Families 2, 3, and 4, effective May 2025, pertains specifically to the operating systems within these families. This retirement doesn't extend the overall support timeline for Azure Cloud Services (classic) beyond the scheduled deprecation in August 2024. [Cloud Services Extended Support](../cloud-services-extended-support/overview.md) continues support with Guest OS Families 5 and newer. 
+The announcement of the retirement of Azure Guest OS Families 2, 3, and 4, effective March 2025, pertains specifically to the operating systems within these families. This retirement doesn't extend the overall support timeline for Azure Cloud Services (classic) beyond the scheduled deprecation in August 2024. [Cloud Services Extended Support](../cloud-services-extended-support/overview.md) continues support with Guest OS Families 5 and newer. 
 
 Customers currently using Azure Cloud Services who wish to continue receiving support beyond August 2024 are encouraged to transition to [Cloud Services Extended Support](../cloud-services-extended-support/overview.md). This separate service offering ensures continued assistance and support. Cloud Services Extended Support requires a distinct enrollment and isn't automatically included with existing Azure Cloud Services subscriptions. 
 

articles/azure-netapp-files/configure-network-features.md

@@ -34,17 +34,17 @@ To add a new step to your workflow by using the Azure Communication Services Ema
 
    1. Under the step where you want to add the new action, select **New step**. Alternatively, to add the new action between steps, move your pointer over the arrow between those steps, select the plus sign (+), and select **Add an action**.
 
-   1. Under the **Choose an operation** search box, select **Standard**. In the search box, enter **Communication Services Email**.
+   1. Under the **Choose an operation** search box, select **Premium**. In the search box, enter **Azure Communication Email**.
 
    1. From the actions list, select **Send email**.
 
-      :::image type="content" source="../media/logic-app/azure-communications-services-connector-send-email.png" alt-text="Screenshot that shows the Azure Communication Services Email connector Send email action."::: 
+      :::image type="content" source="../media/logic-app/azure-communications-services-connector-send-email-general-availability.png" alt-text="Screenshot that shows the Azure Communication Services Email connector Send email action."::: 
 
    **Standard**
 
    1. Under the step where you want to add the new action, select the plus sign (**+**). Alternatively, to add the new action between steps, move your pointer over the arrow between those steps, select the plus sign (+), and select **Add an action**.
 
-   1. Under the **Choose an operation** search box, select **Azure**. In the search box, enter **Communication Services Email**.
+   1. Under the **Add an action** search box, select **Premium** in the runtime dropdown. In the search box, enter **Azure Communication Email**.
 
    1. From the actions list, select **Send email**.
 
@@ -60,9 +60,9 @@ To add a new step to your workflow by using the Azure Communication Services Ema
 
 1. When you're done, select **Create**.
 
-1. In the **From** field, use the email address that you configured in the [prerequisites](#prerequisites). Enter the values for the **To**, **Subject**, and **Body** fields, for example:
+1. In the **From** field, use the email address that you configured in the [prerequisites](#prerequisites). Enter the values for the **To Email**, **Subject**, and **Body** fields, for example:
 
-   :::image type="content" source="../media/logic-app/azure-communications-services-connector-send-email-input.png" alt-text="Screenshot that shows the Azure Communication Services Email connector Send email action input.":::
+   :::image type="content" source="../media/logic-app/azure-communication-services-connector-send-email-input-general-availability.png" alt-text="Screenshot that shows the Azure Communication Services Email connector Send email action input.":::
 
 1. Save your workflow. On the designer toolbar, select **Save**.