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

roygara · roygara · commit d08b1be9db36 · 2020-03-02T10:39:37.000-08:00
diff --git a/articles/active-directory/fundamentals/concept-fundamentals-security-defaults.md b/articles/active-directory/fundamentals/concept-fundamentals-security-defaults.md
@@ -66,7 +66,7 @@ One common method to improve protection for all users is to require a stronger f
 
 To give your users easy access to your cloud apps, Azure AD supports a variety of authentication protocols, including legacy authentication. *Legacy authentication* is a term that refers to an authentication request made by:
 
-- Older Office clients that don't use modern authentication (for example, an Office 2010 client).
+- Clients that don't use modern authentication (for example, an Office 2010 client).
 - Any client that uses older mail protocols such as IMAP, SMTP, or POP3.
 
 Today, the majority of compromising sign-in attempts come from legacy authentication. Legacy authentication does not support Multi-Factor Authentication. Even if you have a Multi-Factor Authentication policy enabled on your directory, an attacker can authenticate by using an older protocol and bypass Multi-Factor Authentication. 
diff --git a/articles/cosmos-db/cosmosdb-monitor-resource-logs.md b/articles/cosmos-db/cosmosdb-monitor-resource-logs.md
@@ -94,7 +94,7 @@ For detailed information about how to create a diagnostic setting by using the A
    | summarize count = count()  by OperationName, requestResourceType_s, bin(TimeGenerated, 1h) 
    ```
 
-1. What is the maximum throughput that a partition provides?
+1. What is the maximum throughput that a partition has consumed?
 
    ```Kusto
    AzureDiagnostics
diff --git a/articles/logic-apps/add-artifacts-integration-service-environment-ise.md b/articles/logic-apps/add-artifacts-integration-service-environment-ise.md
@@ -1,23 +1,25 @@
 ---
-title: Add artifacts to integration service environments
+title: Add resources to integration service environments
 description: Add logic apps, integration accounts, custom connectors, and managed connectors to your integration service environment (ISE)
 services: logic-apps
 ms.suite: integration
 ms.reviewer: klam, logicappspm
 ms.topic: conceptual
-ms.date: 02/10/2020
+ms.date: 02/28/2020
 ---
 
-# Add artifacts to your integration service environment (ISE) in Azure Logic Apps
+# Add resources to your integration service environment (ISE) in Azure Logic Apps
 
-After you create an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), add artifacts such as logic apps, integration accounts, and connectors so that they can access the resources in your Azure virtual network. For example, managed ISE connectors that become available after you create your ISE don't automatically appear in the Logic App Designer. Before you can use these ISE connectors, you have to manually [add and deploy those connectors to your ISE](#add-ise-connectors-environment) so that they appear in the Logic App Designer.
+After you create an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), add resources such as logic apps, integration accounts, and connectors so that they can access the resources in your Azure virtual network. For example, managed ISE connectors that become available after you create your ISE don't automatically appear in the Logic App Designer. Before you can use these ISE connectors, you have to manually [add and deploy those connectors to your ISE](#add-ise-connectors-environment) so that they appear in the Logic App Designer.
 
 ## Prerequisites
 
 * An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
 
 * The ISE that you created to run your logic apps. If you don't have an ISE, [create an ISE first](../logic-apps/connect-virtual-network-vnet-isolated-environment.md).
 
+* To create, add, or update resources that are deployed to an ISE, you need to be assigned the Owner or Contributor role on that ISE, or you have permissions inherited through the Azure subscription or Azure resource group associated with the ISE. For people who don't have owner, contributor, or inherited permissions, they can be assigned the Integration Service Environment Contributor role or Integration Service Environment Developer role. For more information about role-based access control (RBAC), see [What is role-based access control (RBAC) for Azure resources](../role-based-access-control/overview.md)?
+
 <a name="create-logic-apps-environment"></a>
 
 ## Create logic apps
@@ -77,7 +79,7 @@ To create an integration account that uses an ISE, follow these steps:
 
 1. [Link your logic app to your integration account in the usual way](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md#link-account).
 
-1. Continue by adding artifacts to your integration account, such as [trading partners](../logic-apps/logic-apps-enterprise-integration-partners.md) and [agreements](../logic-apps/logic-apps-enterprise-integration-agreements.md).
+1. Continue by adding resources to your integration account, such as [trading partners](../logic-apps/logic-apps-enterprise-integration-partners.md) and [agreements](../logic-apps/logic-apps-enterprise-integration-agreements.md).
 
 1. To manage integration accounts in your ISE, see [Manage your integration service environment](../logic-apps/ise-manage-integration-service-environment.md).
 
diff --git a/articles/logic-apps/connect-virtual-network-vnet-isolated-environment.md b/articles/logic-apps/connect-virtual-network-vnet-isolated-environment.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: klam, logicappspm
 ms.topic: conceptual
-ms.date: 02/13/2020
+ms.date: 02/28/2020
 ---
 
 # Connect to Azure virtual networks from Azure Logic Apps by using an integration service environment (ISE)
diff --git a/articles/logic-apps/logic-apps-limits-and-config.md b/articles/logic-apps/logic-apps-limits-and-config.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: klam, logicappspm
 ms.topic: article
-ms.date: 02/20/2020
+ms.date: 02/28/2020
 ---
 
 # Limits and configuration information for Azure Logic Apps
@@ -191,7 +191,7 @@ Here are the limits for custom connectors that you can create from web APIs.
 | Name | Limit |
 |------|-------|
 | Managed identities per logic app | Either the system-assigned identity or 1 user-assigned identity |
-| Number of logic apps that have a managed identity in an Azure subscription per region | 100 |
+| Number of logic apps that have a managed identity in an Azure subscription per region | 250 |
 |||
 
 <a name="integration-account-limits"></a>
diff --git a/articles/logic-apps/toc.yml b/articles/logic-apps/toc.yml
@@ -109,7 +109,7 @@
         href: connect-virtual-network-vnet-isolated-environment.md
       - name: Set up access for multiple integration service environments
         href: connect-virtual-network-vnet-set-up-single-ip-address.md
-      - name: Add artifacts to integration service environments
+      - name: Add resources to integration service environments
         href: add-artifacts-integration-service-environment-ise.md
       - name: Set up customer-managed encryption keys for integration service environments
         href: customer-managed-keys-integration-service-environment.md
diff --git a/articles/virtual-network/tutorial-create-validate-nat-gateway-portal.md b/articles/virtual-network/tutorial-create-validate-nat-gateway-portal.md
@@ -31,27 +31,24 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
 We'll guide you through configuration of a full test environment and the execution of the tests itself in the next steps. We'll start with the source, which will use the NAT gateway resource we create in later steps.
 
-### Create a virtual network
+## Virtual network and parameters
 
 Before you deploy a VM and can use your NAT gateway, we need to create the resource group and virtual network.
 
-1. On the upper-left side of the screen, select **Create a resource** > **Networking** > **Virtual network**, or search for **Virtual Network** in the Marketplace search.
+In this section you'll need to replace the following parameters in the steps with the information below:
 
-2. In **Create virtual network**, enter or select this information:
+| Parameter                   | Value                |
+|-----------------------------|----------------------|
+| **\<resource-group-name>**  | myResourceGroupNAT |
+| **\<virtual-network-name>** | myVNetsource          |
+| **\<region-name>**          | East US 2      |
+| **\<IPv4 address space>**   | 192.168.0.0\16          |
+| **\<subnet-name>**          | mySubnetsource        |
+| **\<subnet-address-range>** | 192.168.0.0\24          |
 
-    | Setting | Value |
-    | ------- | ----- |
-    | Name | Enter **myVNetsource**. |
-    | Address space | Enter **192.168.0.0/16**. |
-    | Subscription | Select your subscription.|
-    | Resource group | Select create new - **myResourceGroupNAT**. |
-    | Location | Select **East US 2**.|
-    | Subnet - Name | Enter **mySubnetsource**. |
-    | Subnet - Address range | Enter **192.168.0.0/24**. |
-
-3. Leave the rest of the defaults and select **Create**.
+[!INCLUDE [virtual-networks-create-new](../../includes/virtual-networks-create-new.md)]
 
-### Create source virtual machine
+## Create source virtual machine
 
 We'll now create a VM to use the NAT service. This VM has a public IP to use as an instance-level Public IP to allow you to access the VM. NAT service is flow direction aware and will replace the default Internet destination in your subnet. The VM's public IP address won't be used for outbound connections.
 
@@ -156,25 +153,25 @@ All outbound traffic to Internet destinations is now using the NAT service.  It
 
 We'll now create a destination for the outbound traffic translated by the NAT service to allow you to test it.
 
-### Configure virtual network for destination
+
+## Virtual network and parameters for destination
 
 Before you deploy a VM for the destination, we need to create a virtual network where the destination virtual machine can reside. The following are the same steps as for the source VM with some small changes to expose the destination endpoint.
 
-1. On the upper-left side of the screen, select **Create a resource** > **Networking** > **Virtual network**.
+In this section you'll need to replace the following parameters in the steps with the information below:
 
-2. In **Create virtual network**, enter or select this information:
+| Parameter                   | Value                |
+|-----------------------------|----------------------|
+| **\<resource-group-name>**  | myResourceGroupNAT |
+| **\<virtual-network-name>** | myVNetdestination          |
+| **\<region-name>**          | East US 2      |
+| **\<IPv4 address space>**   | 192.168.0.0\16          |
+| **\<subnet-name>**          | mySubnetdestination        |
+| **\<subnet-address-range>** | 192.168.0.0\24          |
 
-    | Setting | Value |
-    | ------- | ----- |
-    | Name | Enter **myVNetdestination**. |
-    | Address space | Enter **192.168.0.0/16**. |
-    | Subscription | Select your subscription.|
-    | Resource group | Select create new - **myResourceGroupNAT**. |
-    | Location | Select **East US 2**.|
-    | Subnet - Name | Enter **mySubnetdestination**. |
-    | Subnet - Address range | Enter **192.168.0.0/24**. |
+[!INCLUDE [virtual-networks-create-new](../../includes/virtual-networks-create-new.md)]
 
-### Create destination virtual machine
+## Create destination virtual machine
 
 1. On the upper-left side of the portal, select **Create a resource** > **Compute** > **Ubuntu Server 18.04 LTS**, or search for **Ubuntu Server 18.04 LTS** in the Marketplace search.
 
