Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr

SnehaGunda · SnehaGunda · commit 50e096863184 · 2020-03-17T16:23:18.000-07:00
diff --git a/articles/app-service/web-sites-monitor.md b/articles/app-service/web-sites-monitor.md
@@ -14,7 +14,7 @@ ms.custom: seodec18
 [Azure App Service](https://go.microsoft.com/fwlink/?LinkId=529714) provides
 built-in monitoring functionality for web apps, mobile, and API apps in the [Azure portal](https://portal.azure.com).
 
-In the Azure portal, you can review *quotas* and *metrics* for an app and App Service plan, and set up *alerts* and *autoscaling* that are based metrics.
+In the Azure portal, you can review *quotas* and *metrics* for an app and App Service plan, and set up *alerts* and *autoscaling* rules based metrics.
 
 ## Understand quotas
 
@@ -60,13 +60,17 @@ You can increase or remove quotas from your app by upgrading your App Service pl
 > **File System Usage** is a new metric being rolled out globally, no data is expected unless you have been whitelisted for private preview.
 > 
 
+> [!IMPORTANT]
+> **Average Response Time** will be deprecated to avoid confusion with metric aggregations. Use **Response Time** as a replacement.
+
 Metrics provide information about the app or the App Service plan's behavior.
 
 For an app, the available metrics are:
 
 | Metric | Description |
 | --- | --- |
-| **Average Response Time** | The average time taken for the app to serve requests, in seconds. |
+| **Response Time** | The time taken for the app to serve requests, in seconds. |
+| **Average Response Time (deprecated)** | The average time taken for the app to serve requests, in seconds. |
 | **Average memory working set** | The average amount of memory used by the app, in megabytes (MiB). |
 | **Connections** | The number of bound sockets existing in the sandbox (w3wp.exe and its child processes).  A bound socket is created by calling bind()/connect() APIs and remains until said socket is closed with CloseHandle()/closesocket(). |
 | **CPU Time** | The amount of CPU consumed by the app, in seconds. For more information about this metric, see [CPU time vs CPU percentage](#cpu-time-vs-cpu-percentage). |
diff --git a/articles/azure-monitor/platform/metrics-supported.md b/articles/azure-monitor/platform/metrics-supported.md
@@ -2168,6 +2168,12 @@ Azure Monitor provides several ways to interact with metrics, including charting
 
 ## Microsoft.Web/sites (excluding functions)
 
+> [!NOTE]
+> **File System Usage** is a new metric being rolled out globally, no data is expected unless you have been whitelisted for private preview.
+
+> [!IMPORTANT]
+> **Average Response Time** will be deprecated to avoid confusion with metric aggregations. Use **Response Time** as a replacement.
+
 |Metric|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|
 |---|---|---|---|---|---|
 |CpuTime|CPU Time|Seconds|Total|CPU Time|Instance|
@@ -2185,7 +2191,8 @@ Azure Monitor provides several ways to interact with metrics, including charting
 |Http5xx|Http Server Errors|Count|Total|Http Server Errors|Instance|
 |MemoryWorkingSet|Memory working set|Bytes|Average|Memory working set|Instance|
 |AverageMemoryWorkingSet|Average memory working set|Bytes|Average|Average memory working set|Instance|
-|AverageResponseTime|Average Response Time|Seconds|Average|Average Response Time|Instance|
+|ResponseTime|Response Time|Seconds|Total|Response Time|Instance|
+|AverageResponseTime|Average Response Time (deprecated)|Seconds|Average|Average Response Time|Instance|
 |AppConnections|Connections|Count|Average|Connections|Instance|
 |Handles|Handle Count|Count|Average|Handle Count|Instance|
 |Threads|Thread Count|Count|Average|Thread Count|Instance|
diff --git a/articles/bastion/TOC.yml b/articles/bastion/TOC.yml
@@ -40,6 +40,14 @@
     href: session-monitoring.md
   - name: Troubleshoot
     href: troubleshoot.md
+- name: Reference
+  items:
+  - name: Azure PowerShell
+    href: /powershell/module/az.network
+  - name: REST
+    href: /rest/api/virtualnetwork/bastionhosts
+  - name: Azure CLI
+    href: /cli/azure/network/bastion
 - name: Resources
   items:
   - name: Bastion FAQ
diff --git a/articles/lighthouse/concepts/managed-services-offers.md b/articles/lighthouse/concepts/managed-services-offers.md
@@ -1,7 +1,7 @@
 ---
 title: Managed services offers in Azure Marketplace
 description: Managed services offers allow service providers to sell resource management offers to customers in Azure Marketplace.
-ms.date: 12/16/2019
+ms.date: 03/17/2020
 ms.topic: conceptual
 ---
 
@@ -26,7 +26,7 @@ Public plans let you promote your services to new customers. These are usually m
 If appropriate, you can include both public and private plans in the same offer.
 
 > [!IMPORTANT]
-> Once a plan has been published as public, you can't change it to private. To control which customers can accept your offer and delegate resources, use a private plan. With a public plan, you can't restrict availability to certain customers or even to a certain number of customers (although you can stop selling the plan completely if you choose to do so). There is currently no mechanism to reject or remove delegations once a customer accepts an offer, although you can always reach out to a customer and ask them to [remove your access](../how-to/view-manage-service-providers.md#add-or-remove-service-provider-offers).
+> Once a plan has been published as public, you can't change it to private. To control which customers can accept your offer and delegate resources, use a private plan. With a public plan, you can't restrict availability to certain customers or even to a certain number of customers (although you can stop selling the plan completely if you choose to do so). You can [remove access to a delegation](../how-to/onboard-customer.md#remove-access-to-a-delegation) after a customer accepts an offer only if you included an **Authorization** with the **Role Definition** set to [Managed Services Registration Assignment Delete Role](../../role-based-access-control/built-in-roles.md#managed-services-registration-assignment-delete-role) when you published the offer. You can also reach out to the  customer and ask them to [remove your access](../how-to/view-manage-service-providers.md#add-or-remove-service-provider-offers).
 
 ## Publish managed service offers
 
diff --git a/articles/sql-database/toc.yml b/articles/sql-database/toc.yml
@@ -155,6 +155,8 @@
         href: sql-database-managed-instance-public-endpoint-securely.md
       - name: Managed instance auditing
         href: sql-database-managed-instance-auditing.md
+    - name: Security baseline	
+      href: security-baseline.md
 
   - name: Connect and query
     href: sql-database-connect-query.md
@@ -557,6 +559,8 @@
           href: sql-database-resource-limits-database-server.md
         - name: Connectivity architecture
           href: sql-database-connectivity-architecture.md 
+        - name: Connectivity settings	
+          href: sql-database-connectivity-settings.md
 
       - name: Data sync
         items:
diff --git a/articles/storage/files/storage-files-planning.md b/articles/storage/files/storage-files-planning.md
@@ -83,7 +83,7 @@ In general, Azure Files features and interoperability with other services are th
     - Standard file shares are available for locally redundant, zone redundant, geo-redundant (GRS), and geo-zone redundant (GZRS) storage.
 - **Maximum size of file share**
     - Premium file shares can be provisioned for up to 100 TiB without any additional work.
-    - By default, standard file shares can span only up to 5 TiB, although the share limit can be increased to 100 TiB by opting into the *large file share* storage account feature flag. Standard file shares may only span up to 100 TiB for locally redundant or zone redundant storage accounts. For more information on increasing  
+    - By default, standard file shares can span only up to 5 TiB, although the share limit can be increased to 100 TiB by opting into the *large file share* storage account feature flag. Standard file shares may only span up to 100 TiB for locally redundant or zone redundant storage accounts. For more information on increasing file share sizes, see [Enable and create large file shares](https://docs.microsoft.com/azure/storage/files/storage-files-how-to-create-large-file-share).
 - **Regional availability**
     - Premium file shares are not available in every region, and zone redundant support is available in a smaller subset of regions. To find out if premium file shares are currently available in your region, see the [products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=storage) page for Azure. To find out what regions support ZRS, see [Azure Availability Zone support by region](../../availability-zones/az-overview.md#services-support-by-region). To help us prioritize new regions and premium tier features, please fill out this [survey](https://aka.ms/pfsfeedback).
     - Standard file shares are available in every Azure region.
diff --git a/articles/storage/queues/media/storage-queues-introduction/queue1.png b/articles/storage/queues/media/storage-queues-introduction/queue1.png
diff --git a/articles/virtual-desktop/overview.md b/articles/virtual-desktop/overview.md
@@ -6,7 +6,7 @@ author: Heidilohr
 
 ms.service: virtual-desktop
 ms.topic: overview
-ms.date: 01/27/2020
+ms.date: 03/12/2020
 ms.author: helohr
 manager: lizross
 ---
@@ -124,6 +124,20 @@ The following Remote Desktop clients support Windows Virtual Desktop:
 * [iOS](connect-ios.md)
 * [Android (Preview)](connect-android.md)
 
+The Remote Desktop clients must have access to the following URLs:
+
+|Address|Outbound port|Purpose|Client(s)|
+|---|---|---|---|
+|*.wvd.microsoft.com|TCP port 443|Service traffic|All|
+|go.microsoft.com|TCP port 443|Microsoft FWLinks|All|
+|aka.ms|TCP port 443|Microsoft URL shortener|All|
+|docs.microsoft.com|TCP port 443|Documentation|All|
+|privacy.microsoft.com|TCP port 443|Privacy statement|All|
+|query.prod.cms.rt.microsoft.com|TCP port 443|Client updates|Windows Desktop|
+
+>[!IMPORTANT]
+>Opening these URLs is essential for a reliable client experience. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to the client sites and resources, and don't include URLs for other services like Azure Active Directory.
+
 ## Supported virtual machine OS images
 
 Windows Virtual Desktop supports the following x64 operating system images:
diff --git a/articles/virtual-machines/workloads/sap/hana-network-architecture.md b/articles/virtual-machines/workloads/sap/hana-network-architecture.md
@@ -167,7 +167,7 @@ In the Azure regions where Global Reach is offered, you can request enabling the
 > In case of using Global Reach for enabling direct access between your HANA Large Instance units and on-premises assets, the network data and control flow is **not routed through Azure virtual networks**, but directly between the Microsoft enterprise exchange routers. As a result any NSG or ASG rules, or any type of firewall, NVA, or proxy you deployed in an Azure virtual network, are not getting touched. **If you use ExpressRoute Global Reach to enable direct access from on-premises to HANA Large instance units restrictions and permissions to access HANA large Instance units need to be defined in firewalls on the on-premises side** 
 
 ##### Connecting HANA Large Instances in different Azure regions
-In the same way, as ExpressRoute Global Reach can be used for connecting on-premises to HANA Large Instance units, it can be used to connect tow HANA Large Instance tenants that are deployed for you in two different regions. The isolation is the ExpressRoute circuits that your HANA Large Instance tenants are using to connect to Azure in both regions. There are no additional charges for connecting two HANA Large Instance tenants that are deployed in two different regions. 
+In the same way, as ExpressRoute Global Reach can be used for connecting on-premises to HANA Large Instance units, it can be used to connect two HANA Large Instance tenants that are deployed for you in two different regions. The isolation is the ExpressRoute circuits that your HANA Large Instance tenants are using to connect to Azure in both regions. There are no additional charges for connecting two HANA Large Instance tenants that are deployed in two different regions. 
 
 > [!IMPORTANT]  
 > The data flow and control flow of the network traffic between the different HANA Large instance tenants will not be routed through azure networks. As a result you can't use Azure functionality or NVAs to enforce communication restrictions between your two HANA Large Instances tenants. 
diff --git a/includes/active-directory-cloud-provisioning-sso.md b/includes/active-directory-cloud-provisioning-sso.md
@@ -9,7 +9,7 @@ ms.author: billmath
 ---
 
 ## Steps to enable Single Sign-on
-Cloud provisioning works with Single Sign-on.  Currently their is not an option to enable SSO when the agent is installed, however you can use the steps below to enable SSO and use it. 
+Cloud provisioning works with Single Sign-on.  Currently there is not an option to enable SSO when the agent is installed, however you can use the steps below to enable SSO and use it. 
 
 ### Step 1: Download and extract Azure AD Connect files
 1.  First, download the latest version of [Azure AD Connect](https://www.microsoft.com/download/details.aspx?id=47594)
diff --git a/includes/virtual-wan-faq-include.md b/includes/virtual-wan-faq-include.md
@@ -9,6 +9,13 @@
  ms.author: cherylmc
  ms.custom: include file
 ---
+### Does the user need to have hub and spoke with SD-WAN/VPN devices to use Azure Virtual WAN?
+
+Virtual WAN provides many functionalities built into a single pane of glass such as Site/Site-to-site VPN connectivity, User/P2S connectivity, ExpressRoute connectivity, Virtual Network connectivity, VPN ExpressRoute Interconnectivity, VNET to VNET transitive connectivity, Centralized Routing, Azure firewall and firewall manager security, Monitoring, ExpressRoute Encryption and many other capabilities. You do not have to have all of these use cases to start using Virtual WAN. You can simply get started with just one use case. The Virtual WAN architecture is a hub and spoke architecture with scale and performance built-in where branches (VPN/SD-WAN devices), users (Azure VPN Clients, openVPN or IKEv2 Clients), ExpressRoute circuits, Virtual Networks serve as spokes to Virtual Hub(s). All hubs are connected in full mesh in a Standard Virtual WAN making it easy for the user to use the Microsoft backbone for any-to-any (any spoke) connectivity. For hub and spoke with SD-WAN/VPN devices, users can either manually set it up in the Azure Virtual WAN portal or use the Virtual WAN Partner CPE (SD-WAN/VPN) to set up connectivity to Azure. Virtual WAN partners provide automation for connectivity which is the ability to export the device info into Azure, download the Azure configuration and establish connectivity to the Azure Virtual WAN hub. For Point-to-site/User VPN connectivity, we support [Azure VPN client](https://go.microsoft.com/fwlink/?linkid=2117554), OpenVPN or IKEv2 client. 
+
+### What client does the Azure Virtual WAN User VPN (Point-to-site) support?
+
+Virtual WAN supports [Azure VPN client](https://go.microsoft.com/fwlink/?linkid=2117554), OpenVPN Client, or any IKEv2 client. Azure AD authentication is supported with Azure VPN Client.A minimum of Windows 10 client OS version 17763.0 or higher is required.  OpenVPN client(s) can support certificate based authentication. Once cert-based auth is selected on the gateway, you will see the .ovpn file to download to your device. Both certificate and RADIUS auth is supported with IKEv2. 
 
 ### What is the difference between an Azure virtual network gateway (VPN Gateway) and an Azure Virtual WAN VPN gateway?
 
