Merge pull request MicrosoftDocs#77068 from MicrosoftDocs/repo_sync_working_branch

tfosmark · web-flow · commit 5bc74c01c503 · 2019-05-17T15:14:57.000-07:00
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
diff --git a/articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md b/articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md
@@ -1344,6 +1344,9 @@ Group resources are identified by the schema identifier, `urn:ietf:params:scim:s
 | objectId |ID |
 | proxyAddresses |emails[type eq "other"].Value |
 
+## Allow IP addresses used by the Azure AD provisioning service to make SCIM requests
+Certain apps allow inbound traffic to their app. In order for the Azure AD provisioning service to function as expected, the IP addresses used must be allowed. For a list of IP addresses for each service tag/region, see the JSON file - [Azure IP Ranges and Service Tags – Public Cloud](https://www.microsoft.com/download/details.aspx?id=56519). You can download and program these IPs into your firewall as needed. The reserved IP ranges for for Azure AD provisioning can be found under "AzureActiveDirectoryDomainServices."
+ 
 
 ## Related articles
 * [Automate User Provisioning/Deprovisioning to SaaS Apps](user-provisioning.md)
diff --git a/articles/active-directory/reports-monitoring/concept-sign-ins.md b/articles/active-directory/reports-monitoring/concept-sign-ins.md
@@ -127,21 +127,29 @@ Possible values are:
 
 When you select a custom timeframe, you can configure a start time and an end time.
 
-If you add additional fields to your sign-ins view, these fields are automatically added to the list of filters. For example, by adding **Client App** field to your list, you also get another filter option that enables you to set the following filters:
-
-- Browser      
-- Exchange ActiveSync (supported)               
-- Exchange ActiveSync (unsupported)
-- Other clients               
-    - IMAP
-    - MAPI
-    - Older Office clients
-    - POP
-    - SMTP
-
-
+If you add additional fields to your sign-ins view, these fields are automatically added to the list of filters. For example, by adding **Client App** field to your list, you also get another filter option that enables you to set the following filters:  
 ![Sign-in activity](./media/concept-sign-ins/12.png "Sign-in activity")
 
+- **Browser**  
+    This filter shows all events where sign-in attempts were performed using browser flows.
+- **Exchange ActiveSync (supported)**  
+    This filter shows all sign-in attempts where the Exchange ActiveSync (EAS) protocol has been attempted from supported platforms like iOS, Android and Windows Phone.
+- **Exchange ActiveSync (unSupported)**  
+    This filter shows all sign-in attempts where the EAS protocol has been attempted from unsupported platforms like, Linux distros.
+- **Mobile Apps and Desktop clients**
+        This filter shows all sign-in attempts that were not using browser flows. This can be mobile apps from any platform using any protocol or from Desktop client apps like Office on Windows or MacOS.
+  
+- **Other clients**
+    - **IMAP**  
+        A legacy mail client using IMAP to retrieve email.
+    - **MAPI**  
+        Office 2013, where ADAL is enabled and it is using MAPI.
+    - **Older Office clients**  
+        Office 2013 in its default configuration where ADAL is not enabled and it is using MAPI, or Office 2016 where ADAL has been disabled.
+    - **POP**  
+        A legacy mail client using POP3 to retrieve email.
+    - **SMTP**  
+        A legacy mail client using SMTP to send email.
 
 ## Download sign-in activities
 
diff --git a/articles/openshift/howto-setup-environment.md b/articles/openshift/howto-setup-environment.md
@@ -25,14 +25,16 @@ To build and run Microsoft Azure Red Hat OpenShift applications, you'll need to:
 
 The following instructions will walk you through all of these prerequisites.
 
-## Purchase Azure virtual machine reserved instances
+## Purchase Azure Red Hat OpenShift application nodes reserved instances
 
-Before you can use Azure Red Hat OpenShift, you'll need to purchase Azure virtual machine reserved instances.
+Before you can use Azure Red Hat OpenShift, you'll need to purchase a minimum of 4 Azure Red Hat OpenShift reserved application nodes, after which you'll be able to provision clusters.
 
-If you are an Azure customer, here's how to [purchase Azure virtual machine reserved instances](https://aka.ms/openshift/buy). A reservation reduces your spend by pre-paying for fully managed Azure services. Refer to [*What are Azure Reservations*](https://docs.microsoft.com/azure/billing/billing-save-compute-costs-reservations) to learn more about reservations and how they save you money.
+If you are an Azure customer,[purchase Azure Red Hat OpenShift reserved instances](https://aka.ms/openshift/buy) through the Azure portal. After purchasing, your subscription will be activated within 24 hours.
 
 If you are not an Azure customer, [contact sales](https://aka.ms/openshift/contact-sales) and fill out the sales form at the bottom of the page to start the process.
 
+Refer to the [Azure Red Hat OpenShift pricing page](https://aka.ms/openshift/pricing) for more information.
+
 ## Install the Azure CLI
 
 Azure Red Hat OpenShift requires version 2.0.65 or higher of the Azure CLI. If you've already installed the Azure CLI, you can check which version you have by running:
@@ -109,4 +111,4 @@ Try the tutorial:
 > [!div class="nextstepaction"]
 > [Create an Azure Red Hat OpenShift cluster](tutorial-create-cluster.md)
 
-[azure-cli-install]: https://docs.microsoft.com/cli/azure/install-azure-cli
+[azure-cli-install]: https://docs.microsoft.com/cli/azure/install-azure-cli
diff --git a/articles/openshift/openshift-faq.md b/articles/openshift/openshift-faq.md
@@ -14,6 +14,16 @@ ms.date: 05/08/2019
 
 This article addresses frequently asked questions (FAQs) about Microsoft Azure Red Hat OpenShift.
 
+## How do I get started?
+
+Before you can use Azure Red Hat OpenShift, you'll need to purchase a minimum of 4 Azure Red Hat OpenShift reserved application nodes.
+
+If you are an Azure customer,[purchase Azure Red Hat OpenShift reserved instances](https://aka.ms/openshift/buy) through the Azure portal. After purchasing, your subscription will be activated within 24 hours, after which you'll be able to provision clusters.
+
+If you are not an Azure customer, [contact sales](https://aka.ms/openshift/contact-sales) and fill out the sales form at the bottom of the page to start the process.
+
+Refer to the [Azure Red Hat OpenShift pricing page](https://aka.ms/openshift/pricing) for more information.
+
 ## Which Azure regions are supported?
 
 See [Supported resources](supported-resources.md#azure-regions) for a list of global regions where Azure Red Hat OpenShift is supported.
@@ -66,4 +76,4 @@ No. All resources, including the cluster master, run in your customer subscripti
 
 ## Is Open Service Broker for Azure (OSBA) supported?
 
-Yes. You can use OSBA with Azure Red Hat OpenShift. See [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure#openshift-project-template) for more information.
+Yes. You can use OSBA with Azure Red Hat OpenShift. See [Open Service Broker for Azure](https://github.com/Azure/open-service-broker-azure#openshift-project-template) for more information.
diff --git a/articles/openshift/tutorial-create-cluster.md b/articles/openshift/tutorial-create-cluster.md
@@ -31,7 +31,7 @@ In this tutorial series you learn how to:
 > [!IMPORTANT]
 > This tutorial requires version 2.0.65 of the Azure CLI.
 >    
-> Before you can use Azure Red Hat Openshift, you need to purchase Azure virtual machine reserved instances as described in [Set up your Azure Red Hat Openshift development environment](howto-setup-environment.md#purchase-azure-virtual-machine-reserved-instances).
+> Before you can use Azure Red Hat Openshift, you need to purchase Azure virtual machine reserved instances as described in [Set up your Azure Red Hat Openshift development environment](howto-setup-environment.md#purchase-azure-red-hat-openshift-application-nodes-reserved-instances).
 
 Before you begin this tutorial:
 
@@ -206,4 +206,4 @@ In this part of the tutorial, you learned how to:
 
 Advance to the next tutorial:
 > [!div class="nextstepaction"]
-> [Scale an Azure Red Hat OpenShift cluster](tutorial-scale-cluster.md)
+> [Scale an Azure Red Hat OpenShift cluster](tutorial-scale-cluster.md)
diff --git a/articles/virtual-network/create-vm-accelerated-networking-cli.md b/articles/virtual-network/create-vm-accelerated-networking-cli.md
@@ -221,6 +221,11 @@ vf_tx_dropped: 0
 ```
 Accelerated Networking is now enabled for your VM.
 
+## Handle dynamic binding and revocation of virtual function 
+Applications must run over the synthetic NIC that is exposed in VM. If the application runs directly over the VF NIC, it doesn't receive **all** packets that are destined to the VM, since some packets show up over the synthetic interface.
+If you run an application over the synthetic NIC, it guarantees that the application receives **all** packets that are destined to it. It also makes sure that the application keeps running, even if the VF is revoked when the host is being serviced. 
+Applications binding to the synthetic NIC is a **mandatory** requirement for all applications taking advantage of **Accelerated Networking**.
+
 ## Enable Accelerated Networking on existing VMs
 If you have created a VM without Accelerated Networking, it is possible to enable this feature on an existing VM.  The VM must support Accelerated Networking by meeting the following prerequisites that are also outlined above:
 
