Merge pull request #9563 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-19 22:00 UTC

Author: learn-build-service-prod[bot]

.github/workflows/create-ado-workitem.yml

@@ -0,0 +1,36 @@
+name: Create Azure DevOps CI on PR
+
+on:
+  pull_request:
+    types: [opened]
+
+jobs:
+  create-work-item:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create Azure DevOps Task
+        env:
+          ADO_ORG_URL: https://dev.azure.com/KMOps
+          ADO_PROJECT: ContentExperience
+          ADO_PAT: ${{ secrets.ADO_PAT }}
+        run: |
+          PR_TITLE="${{ github.event.pull_request.title }}"
+          PR_BODY="${{ github.event.pull_request.body }}"
+          PR_URL="${{ github.event.pull_request.html_url }}"
+
+          curl -X POST \
+            -H "Content-Type: application/json-patch+json" \
+            -H "Authorization: Basic $(echo -n ":$ADO_PAT" | base64)" \
+            $ADO_ORG_URL/$ADO_PROJECT/_apis/wit/workitems/$ExternalCI?api-version=6.0 \
+            -d '[
+              {
+                "op": "add",
+                "path": "/fields/System.Title",
+                "value": "PR Opened: '"$PR_TITLE"'"
+              },
+              {
+                "op": "add",
+                "path": "/fields/System.Description",
+                "value": "Pull Request URL: '"$PR_URL"'\n\n'"$PR_BODY"'"
+              }
+            ]'

support/azure/general/zonal-enablement-request-for-restricted-vm-series.md

@@ -0,0 +1,48 @@
+---
+title: Zonal enablement request for restricted vm series
+description: Guidance to request access to restricted vm series in selected zones.
+ms.date: 08/06/2025
+ms.service: azure-common-issues-support
+ms.author: zmazieva
+author: zmazieva78MS
+ms.reviewer: v-liuamson
+---
+# Zonal enablement request for restricted virtual machine series  
+
+Zonal enablement requests allow customers to select specific zones in a region when requesting access to restricted virtual machine series. 
+
+## Step 1: Create a support request
+
+This guide explains how to request restricted virtual machine series in a specific zone using Help + Support path in the **Azure Portal**.
+
+1. Log into the [Azure Portal](https://portal.azure.com) and navigate to **Help + support**, then select **Create a support request**.
+1. Type in **quotas** in the **Describe your issue** search bar.
+1. Select **Service and Subscription Limits (quotas)** click **Create a support request**
+1. In the **New support request** page, complete the following:
+    1. In **Issue Type**, select **Service and Subscription Limits (quotas)**.
+    1. In **Subscription**, select the relevant subscription for which you would like to request access.
+    1. In **Quota type**, select **Compute-VM (cores-vCPUs) subscription limit increases** proceed next.
+ 
+## Step 2: Provide problem details
+
+1. In the **Problem details** section, select **Enter details**.
+1. Select **Resource Manager** in the **Deployment model**.
+1. Select **Zone access** in the **Choose request types**.
+1. In the **Request details** section select preferred regions in **Locations**
+1. In the displayed region boxes, select the appropriate zone from the **Select requested logical zone** dropdown list.
+1. Then select the VM series you would like to request.
+1. Select **Save and continue**.
+> [!Note]
+> Multiple regions and zones can be selected in one support request.
+
+## Step 3: Review and Submit
+1. Review and fill in the details for the best way to contact you.
+1. Select **Create** to submit the request.
+
+## Request processing
+
+Once you create the support request, the ticket follows our standard process. The confirmation, including your support ticket number, will be sent to your registered email address. If the support team has other questions, they contact you using the communication method you specified in your request.
+
+## Tracking request status
+
+Status of the Quota request can be monitored through **Help + Support/Overview** or **Help + Support/All support requests** in Azure Portal.

support/windows-server/toc.yml

@@ -2754,6 +2754,8 @@ items:
     items:
     - name: Antivirus exclusions for Hyper-V hosts
       href: ./virtualization/antivirus-exclusions-for-hyper-v-hosts.md
+    - name: Block users from running Hyper-V and VMware virtual machines on workstation-class computers
+      href: ./virtualization/block-users-from-running-virtualization-features-on-specific-computers.md
     - name: Issues when starting VM or installing Hyper-V
       href: ./virtualization/bios-update-for-hyper-v.md
     - name: Run programs on non-Microsoft hardware virtualization software

support/windows-server/virtualization/block-users-from-running-virtualization-features-on-specific-computers.md

@@ -0,0 +1,72 @@
+---
+title: How to Block Users from Running Hyper-V and VMware Virtual Machines on Workstation-class Computers
+description: Describes how to block users from installing Hyper-V or other virtualization software on specific computers.
+ms.date: 08/15/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika
+ms.custom:
+- sap:virtualization and hyper-v\installation and configuration of hyper-v
+- pcy:WinComm Storage High Avail
+---
+
+# Block users from running Hyper-V and VMware VMs on workstation-class computers
+
+This article provides guidance for how to use Windows PowerShell or Group Policy to block users from running virtualization software, such as Hyper-V and VMware, on workstation-class computers. These procedures apply to scenarios in which you want to prevent virtualization software from running on both domain-joined and non-domain-joined computers, regardless of a user's administrative permissions.
+
+*Applies to:* Hyper-V Server 2019
+
+## How to block virtualization services
+
+> [!IMPORTANT]  
+>
+> - Before you make these changes in a production environment, test them in a lab environment. This step helps make sure that the changes (especially Group Policy changes) produce the intended results and don't introduce operational issues.
+> - Make sure that you have Administrator permissions on the workstation computers.
+
+### How to block the Hyper-V feature on a single computer
+
+1. On the computer, open an administrative Windows PowerShell window.
+1. Run the following cmdlets, in sequence:
+
+   ```powershell
+   Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
+   bcdedit /set hypervisorlaunchtype off
+   ```
+
+   The first cmdlet removes Hyper-V from the set of available optional features. The second cmdlet prevents Hyper-V from running.
+
+### How to use Group Policy to block Hyper-V services on multiple computers
+
+To configure an appropriate policy, follow these steps:  
+
+1. In the Group Policy Management Console (GPMC), navigate to or create a Group Policy Object (GPO) that applies to the affected computers.
+1. Right-click the GPO, and then select **Edit**. In the Group Policy Editor, select **Computer Configuration** > **Windows Settings** > **Security Settings** > **System Services**.
+1. Configure each service that's related to Hyper-V (for example, Hyper-V Virtual Machine Management). For each of these services, follow these steps:
+   1. Right-click the service, and then select **Properties**.
+   1. In the **Properties** dialog box, select **Define this policy setting**, select **Disabled**, and then select **OK**.
+1. To propagate the policy change, restart all the target computers.
+
+For more information about how to use Group Policy, see [Advanced Group Policy Management](/microsoft-desktop-optimization-pack/agpm/).
+
+## How to use Group Policy to block VMware Workstation services
+
+To configure an appropriate policy, follow these steps:  
+
+1. In the GPMC, navigate to or create a GPO that applies to the affected computers.
+1. Right-click the GPO, and then select **Edit**. In the Group Policy Editor, select **Computer Configuration** > **Policies** > **Windows Settings** > **Security Settings** > **System Services**.
+
+To block users from running VMware Workstation, follow these steps:
+
+1. Create a path rule in **Software Restriction Policies**:
+
+   1. Open the GPMC, and go to **Computer Configuration** > **Policies** > **Policies** > **Windows Settings** > **Software Restriction Policies**.
+   1. If there aren't any software restriction policies, right-click **Software Restriction Policies**, and then select **New Software Restriction Policies**.
+   1. Right-click **Additional Rules**, and then select **New path rule**.
+   1. In the **Path** box, specify the path to the VMware executable files (for example, type *C:\\Program Files (x86)\\VMware\\*, or enter the path to specific .exe files).
+   1. Select **Security level**, and then select **Disallowed**.
+   1. Select **OK**.
+
+1. To propagate the policy change, restart all the target computers.
+
+For more information about how to use Group Policy, see [Advanced Group Policy Management](/microsoft-desktop-optimization-pack/agpm/).