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

Author: greg-lindsay

articles/automation/troubleshoot/hybrid-runbook-worker.md

@@ -4,7 +4,7 @@ description: This article tells how to troubleshoot and resolve issues that aris
 services: automation
 ms.date: 09/17/2023
 ms.topic: troubleshooting
-ms.custom: linux-related-content, has-azure-ad-ps-ref
+ms.custom: linux-related-content, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
 ---
 
 # Troubleshoot agent-based Hybrid Runbook Worker issues in Automation
@@ -339,7 +339,7 @@ Hybrid workers send [Runbook output and messages](../automation-runbook-output-a
 
 #### Issue
 
-A script running on a Windows Hybrid Runbook Worker can't connect as expected to Microsoft 365 on an Orchestrator sandbox. The script is using [Connect-MsolService](/powershell/module/msonline/connect-msolservice) for connection.
+A script running on a Windows Hybrid Runbook Worker can't connect as expected to Microsoft 365 on an Orchestrator sandbox. The script is using [Connect-MgGraph](/powershell/microsoftgraph/authentication-commands#using-connect-mggraph) for connection.
 
 If you adjust **Orchestrator.Sandbox.exe.config** to set the proxy and the bypass list, the sandbox still doesn't connect properly. A **Powershell_ise.exe.config** file with the same proxy and bypass list settings seems to work as you expect. Service Management Automation (SMA) logs and PowerShell logs don't provide any information about proxy.​
 
@@ -349,14 +349,14 @@ The connection to Active Directory Federation Services (AD FS) on the server can
 
 #### Resolution
 
-You can resolve the issue for the Orchestrator sandbox by migrating your script to use the Microsoft Entra modules instead of the MSOnline module for PowerShell cmdlets. For more information, see [Migrating from Orchestrator to Azure Automation (Beta)](../automation-orchestrator-migration.md).
+You can resolve the issue for the Orchestrator sandbox by migrating your script to use the Microsoft Entra modules instead of the PowerShell cmdlets. For more information, see [Migrating from Orchestrator to Azure Automation (Beta)](../automation-orchestrator-migration.md).
 
-​If you want to continue to use the MSOnline module cmdlets, change your script to use [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command). Specify values for the `ComputerName` and `Credential` parameters.
+​If you want to continue to use the module cmdlets, change your script to use [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command). Specify values for the `ComputerName` and `Credential` parameters.
 
 ```powershell
 $Credential = Get-AutomationPSCredential -Name MyProxyAccessibleCredential​
 Invoke-Command -ComputerName $env:COMPUTERNAME -Credential $Credential
-{ Connect-MsolService … }​
+{ Connect-MgGraph … }​
 ```
 
 This code change starts an entirely new PowerShell session under the context of the specified credentials. It should enable the traffic to flow through a proxy server that's authenticating the active user.

articles/azure-functions/TOC.yml

@@ -937,6 +937,9 @@
             - name: Output
               href: functions-bindings-service-bus-output.md
               displayName: Service Bus
+            - name: Migrate version 4.x to 5.x
+              href: migrate-service-bus-version-4-version-5.md
+              displayName: Service Bus
         - name: SignalR Service
           items:
             - name: Overview

articles/azure-vmware/configure-dns-azure-vmware-solution.md

@@ -4,8 +4,8 @@ description: Learn how to configure DNS forwarder for Azure VMware Solution usin
 ms.topic: how-to
 ms.custom: engagement-fy23
 ms.service: azure-vmware
-ms.date: 12/05/2023
-#Customer intent: As an Azure service administrator, I want to <define conditional forwarding rules for a desired domain name to a desired set of private DNS servers via the NSX-T Data Center DNS Service.>
+ms.date: 2/27/2024
+#Customer intent: As an Azure service administrator, I want to <define conditional forwarding rules for a desired domain name to a desired set of private DNS servers via the NSX-T Data Center DNS Service.
 ---
 
 # Configure a DNS forwarder in the Azure portal
@@ -25,14 +25,12 @@ This capability uses the DNS Forwarder Service in NSX-T Data Center. A DNS servi
 >[!TIP]
 >If desired, you can also use the conditional forwarding rules for workload segments by configuring virtual machines on those segments to use the NSX-T Data Center DNS Service IP address as their DNS server.
 
-
 ## Architecture
 
 The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries to DNS systems hosted in Azure and on-premises environments.
 
 :::image type="content" source="media/networking/dns/dns-forwarder-diagram.png" alt-text="Diagram showing that the NSX-T DNS Service can forward DNS queries to DNS systems hosted in Azure and on-premises environments." border="false":::
 
-
 ## Configure DNS forwarder
 
 1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **DNS** > **DNS zones**. Then select **Add**.
@@ -60,7 +58,6 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
    >[!TIP]
    >For private clouds created on or after July 1, 2021, you can ignore the message about a default DNS zone as one is created for you during private cloud creation.
 
-
    >[!IMPORTANT]
    >While certain operations in your private cloud may be performed from NSX-T Manager, for private clouds created on or after July 1, 2021, you _must_ edit the DNS service from the Simplified Networking experience in the Azure portal for any configuration changes made to the default Tier-1 Gateway.  
 
@@ -78,7 +75,6 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
    1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **DNS** > **DNS zones** > Check **TNT##-DNS-FORWARDER-ZONE**.  Then select **Edit**.
 
    ![AVS-DNS](https://user-images.githubusercontent.com/7501186/226980095-b0576824-e1b7-46dc-b726-58670e4e3096.png)
-
 
    2. Change DNS server entries to valid reachable IP addresses.  Then select **OK**
 
@@ -91,7 +87,7 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
 
 After you configure the DNS forwarder, you have some options available to verify name resolution operations. 
 
-### NSX-T Manager
+### VMware NSX-T Manager
 
 NSX-T Manager provides the DNS Forwarder Service statistics at the global service level and on a per zone basis. 
 
@@ -105,7 +101,6 @@ NSX-T Manager provides the DNS Forwarder Service statistics at the global servic
 
    :::image type="content" source="media/networking/dns/nsxt-manager-dns-services-statistics.png" alt-text="Screenshot showing the DNS Forwarder statistics.":::
 
-
 ### PowerCLI
 
 The NSX-T Policy API lets you run nslookup commands from the NSX-T Data Center DNS Forwarder Service. The required cmdlets are part of the `VMware.VimAutomation.Nsxt` module in PowerCLI. The following example demonstrates output from version 12.3.0 of that module.