Merge pull request #11291 from MicrosoftDocs/main639105052069963529sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

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

docs/install/configure-policies-for-enterprise-deployments.md

@@ -55,7 +55,7 @@ The registry settings in this section control how and where the Visual Studio pr
 | `DisableRollback`                | `REG_DWORD`                 | 0                                                   | **Disable the ability to rollback or undo a Visual Studio update**: if set to 1, then users will be prevented from accessing the rollback capability, which prevents Visual Studio from reverting the most recent update, which may contain a security fix. If set to 0 or missing entirely, then users are able to access the rollback feature in Visual Studio, and undo an update and roll back their Visual Studio instances to the previously installed version. For more information, see the [Rollback blog post](https://aka.ms/vs/rollback).|
 | `HideAvailableTab`               | `REG_DWORD`                 | 0                                                   | **Hide the installer's Available tab**:  if set to 1, then administrators are able to hide the installer's **Available** tab, which can prevent users within the organization from accidentally installing the wrong product. |
 | `DisableSound`                   | `REG_DWORD`                 | 0                                                   | **Disable sounds in the installer**: if set to 1, then users are able to disable sounds in the Visual Studio Installer, which will prevent any audio cue when an installer operation is done or when there is an error. Installer operations include install, update, modify, and many other operations done by the installer or any error dialogs while trying the requested operation. If set to 0 or missing entirely, then users are able to re-enable sounds in the installer. For more information, see the [DisableSound blog post](https://aka.ms/vs/disablesound). |
-| `DisableMigrationDialog`  | `REG_DWORD`   | 0           | **Disable the stale-build migration dialog**: if set to 1, it prevents users from seeing the dialog that prompts them to update to the latest version of the Visual Studio IDE. This policy applies to Visual Studio 2026 and later. Insiders and Community scenarios aren't supported. |
+| `DisableMigrationDialog`  | `REG_DWORD`   | 0           | **Disable the stale-build migration dialog**: if set to 1, it prevents users from seeing the dialog that prompts them to update to the latest version of the Visual Studio IDE. This policy applies to Visual Studio 2026 and later. Insiders and Community scenarios aren't supported. **This is currently only available on the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=104405) it will be available on Intune soon**|
 
 > [!IMPORTANT]
 > If you change the `CachePath` registry policy after any installations, you must move the existing package cache to the new location and make sure it's secured so that `SYSTEM` and `Administrators` have **Full Control** and that `Everyone` has **Read** access.