Merge pull request #111676 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/active-directory/users-groups-roles/users-bulk-download.md

@@ -22,7 +22,7 @@ Azure Active Directory (Azure AD) supports bulk user import (create) operations.
 
 ## Required permissions
 
-To download the list of users from the Azure AD admin center, you must be signed in with a user assigned to one or more organization-level administrator roles in Azure AD. Guest inviter and application developer are not considered administrator roles.
+To download the list of users from the Azure AD admin center, you must be signed in with a user assigned to one or more organization-level administrator roles in Azure AD (User Administrator is the minimum role required). Guest inviter and application developer are not considered administrator roles.
 
 ## To download a list of users
 

articles/azure-monitor/app/worker-service.md

@@ -204,9 +204,9 @@ Following is the code for `TimedHostedService` where the background task logic r
             {
                 _logger.LogWarning("A sample warning message. By default, logs with severity Warning or higher is captured by Application Insights");
                 _logger.LogInformation("Calling bing.com");
-                var res = await httpClient.GetAsync("https://bing.com");
+                var res = httpClient.GetAsync("https://bing.com").GetAwaiter().GetResult();
                 _logger.LogInformation("Calling bing completed with status:" + res.StatusCode);
-                telemetryClient.TrackEvent("Bing call event completed");
+                _telemetryClient.TrackEvent("Bing call event completed");
             }
         }
     }

articles/sql-database/sql-database-managed-instance-connect-app.md

@@ -129,6 +129,8 @@ For troubleshooting connectivity issues, review the following:
 
 - If using VNet peering, ensure that you have followed the instructions for setting [Allow Gateway Transit and Use Remote Gateways](#connect-from-on-premises-with-vnet-peering).
 
+- If using VNet peering to connect an Azure App Service hosted application, and the Managed Instance VNet has a public IP address range, make sure that your hosted application settings allow your outbound traffic to be routed to public IP networks. Follow the instructions in [Regional VNet Integration](../app-service/web-sites-integrate-with-vnet.md#regional-vnet-integration).
+
 ## Required versions of drivers and tools
 
 The following minimal versions of the tools and drivers are recommended if you want to connect to Managed Instance: