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

Author: davidsmatlak

articles/active-directory/reports-monitoring/howto-manage-inactive-user-accounts.md

@@ -14,7 +14,7 @@ ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 03/11/2020
+ms.date: 04/07/2020
 ms.author: markvi
 ms.reviewer: dhanyahk
 
@@ -62,11 +62,14 @@ No.
 
 ### What edition of Azure AD do I need to access the property?
 
-To access this property using the related API, you need an Azure AD Premium edition.
+You can access this property in all editions of Azure AD.
 
 ### What permission do I need to read the property?
 
-To read this property, you need to grant the following right: **AuditLogs.Read.All** 
+To read this property, you need to grant the following rights: 
+
+- AuditLogs.Read.All
+- Organisation.Read.All  
 
 
 ### When does Azure AD update the property?
@@ -78,7 +81,7 @@ Each interactive sign-in that was successful results in an update of the underly
 
 To generate a lastSignInDateTime timestamp, you need a successful sign-in. Because the lastSignInDateTime property is a new feature, the value of the lastSignInDateTime property can be blank if:
 
-- The last successful sign-in of a user took place before this feature was released.
+- The last successful sign-in of a user took place before this feature was released (12/01/2019).
 - The affected user account was never used for a successful sign-in.
 
 ## Next steps

articles/aks/servicemesh-istio-install.md

@@ -92,7 +92,10 @@ The [Helm][helm] installation approach for Istio will be deprecated in the futur
 > Istio currently must be scheduled to run on Linux nodes. If you have Windows Server nodes in your cluster, you must ensure that the Istio pods are only scheduled to run on Linux nodes. We'll use [node selectors][kubernetes-node-selectors] to make sure pods are scheduled to the correct nodes.
 
 > [!CAUTION]
-> The [SDS (secret discovery service)][istio-feature-sds] and [Istio CNI][istio-feature-cni] Istio features are currently in [Alpha][istio-feature-stages], so thought should be given before enabling these. In addition, the [Service Account Token Volume Projection][kubernetes-feature-sa-projected-volume] Kubernetes feature (a requirement for SDS) is not enabled in current AKS versions.
+> The [SDS (secret discovery service)][istio-feature-sds] and [Istio CNI][istio-feature-cni] Istio features are currently in [Alpha][istio-feature-stages], so thought should be given before enabling these. 
+>
+> Note that the [Service Account Token Volume Projection][kubernetes-feature-sa-projected-volume] Kubernetes feature (a requirement for SDS) is now **enabled** for all Kubernetes 1.13 and higher versions on AKS.
+
 Create a file called `istio.aks.yaml` with the following content. This file will hold the [Istio control plane spec][istio-control-plane] details for configuring Istio.
 
 ```yaml

articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md

@@ -1,20 +1,16 @@
 ---
 title: Integration and automation platform options in Azure 
-description: "Compare Microsoft cloud services that are optimized for integration tasks: Microsoft Flow, Logic Apps, Functions, and WebJobs."
+description: "Compare Microsoft cloud services that are optimized for integration tasks: Power Automate, Logic Apps, Functions, and WebJobs."
 ms.topic: overview
 ms.date: 04/09/2018
 ms.custom: mvc
 #Customer intent: As a developer, I want to understand the choices that Azure offers for hosting and executing my business logic so that I can choose the right set of Azure services.
 ---
-> [!NOTE]
-> Microsoft Flow is now Power Automate. For more information, see this [blog](https://aka.ms/flow-now-pa).
-> 
-> This content will be updated to reflect the branding change in the coming days.
 # Choose the right integration and automation services in Azure
 
 This article compares the following Microsoft cloud services:
 
-* [Microsoft Flow](https://flow.microsoft.com/)
+* [Microsoft Power Automate](https://flow.microsoft.com/) (was Microsoft Flow)
 * [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps/)
 * [Azure Functions](https://azure.microsoft.com/services/functions/)
 * [Azure App Service WebJobs](../app-service/webjobs-create.md)
@@ -23,23 +19,23 @@ All of these services can solve integration problems and automate business proce
 
 If you're looking for a more general comparison between Azure Functions and other Azure compute options, see [Criteria for choosing an Azure compute service](/azure/architecture/guide/technology-choices/compute-comparison) and [Choosing an Azure compute option for microservices](/azure/architecture/microservices/design/compute-options).
 
-## Compare Microsoft Flow and Azure Logic Apps
+## Compare Microsoft Power Automate and Azure Logic Apps
 
-Microsoft Flow and Logic Apps are both *designer-first* integration services that can create workflows. Both services integrate with various SaaS and enterprise applications. 
+Power Automate and Logic Apps are both *designer-first* integration services that can create workflows. Both services integrate with various SaaS and enterprise applications. 
 
-Microsoft Flow is built on top of Logic Apps. They share the same workflow designer and the same [connectors](../connectors/apis-list.md). 
+Power Automate is built on top of Logic Apps. They share the same workflow designer and the same [connectors](../connectors/apis-list.md). 
 
-Microsoft Flow empowers any office worker to perform simple integrations (for example, an approval process on a SharePoint Document Library) without going through developers or IT. Logic Apps can also enable advanced integrations (for example, B2B processes) where enterprise-level Azure DevOps and security practices are required. It's typical for a business workflow to grow in complexity over time. Accordingly, you can start with a flow at first, and then convert it to a logic app as needed.
+Power Automate empowers any office worker to perform simple integrations (for example, an approval process on a SharePoint Document Library) without going through developers or IT. Logic Apps can also enable advanced integrations (for example, B2B processes) where enterprise-level Azure DevOps and security practices are required. It's typical for a business workflow to grow in complexity over time. Accordingly, you can start with a flow at first, and then convert it to a logic app as needed.
 
-The following table helps you determine whether Microsoft Flow or Logic Apps is best for a particular integration:
+The following table helps you determine whether Power Automate or Logic Apps is best for a particular integration:
 
-|  | Microsoft Flow | Logic Apps |
+|  | Power Automate | Logic Apps |
 | --- | --- | --- |
 | **Users** |Office workers, business users, SharePoint administrators |Pro integrators and developers, IT pros |
 | **Scenarios** |Self-service |Advanced integrations |
 | **Design tool** |In-browser and mobile app, UI only |In-browser and [Visual Studio](../logic-apps/logic-apps-deploy-from-vs.md), [Code view](../logic-apps/logic-apps-author-definitions.md) available |
 | **Application lifecycle management (ALM)** |Design and test in non-production environments, promote to production when ready |Azure DevOps: source control, testing, support, automation, and manageability in [Azure Resource Manager](../logic-apps/logic-apps-create-deploy-azure-resource-manager-templates.md) |
-| **Admin experience** |Manage Microsoft Flow environments and data loss prevention (DLP) policies, track licensing: [Microsoft Flow Admin Center](https://admin.flow.microsoft.com) |Manage resource groups, connections, access management, and logging: [Azure portal](https://portal.azure.com) |
+| **Admin experience** |Manage Power Automate environments and data loss prevention (DLP) policies, track licensing: [Admin center](https://admin.flow.microsoft.com) |Manage resource groups, connections, access management, and logging: [Azure portal](https://portal.azure.com) |
 | **Security** |Office 365 Security and Compliance audit logs, DLP, [encryption at rest](https://wikipedia.org/wiki/Data_at_rest#Encryption) for sensitive data |Security assurance of Azure: [Azure security](https://www.microsoft.com/en-us/trustcenter/Security/AzureSecurity), [Azure Security Center](https://azure.microsoft.com/services/security-center/), [audit logs](https://azure.microsoft.com/blog/azure-audit-logs-ux-refresh/) |
 
 ## Compare Azure Functions and Azure Logic Apps
@@ -102,25 +98,25 @@ For other scenarios where you want to run code snippets for integrating Azure or
 
 <a name="together"></a>
 
-## Microsoft Flow, Logic Apps, Functions, and WebJobs together
+## Power Automate, Logic Apps, Functions, and WebJobs together
 
 You don't have to choose just one of these services. They integrate with each other as well as they do with external services.
 
 A flow can call a logic app. A logic app can call a function, and a function can call a logic app. See, for example, [Create a function that integrates with Azure Logic Apps](functions-twitter-email.md).
 
-The integration between Microsoft Flow, Logic Apps, and Functions continues to improve over time. You can build something in one service and use it in the other services.
+The integration between Power Automate, Logic Apps, and Functions continues to improve over time. You can build something in one service and use it in the other services.
 
 You can get more information on integration services by using the following links:
 
 * [Leveraging Azure Functions & Azure App Service for integration scenarios by Christopher Anderson](https://www.biztalk360.com/integrate-2016-resources/leveraging-azure-functions-azure-app-service-integration-scenarios/)
 * [Integrations Made Simple by Charles Lamanna](https://www.biztalk360.com/integrate-2016-resources/integrations-made-simple/)
 * [Logic Apps Live webcast](https://aka.ms/logicappslive)
-* [Microsoft Flow frequently asked questions](/power-automate/frequently-asked-questions)
+* [Power Automate frequently asked questions](/power-automate/frequently-asked-questions)
 
 ## Next steps
 
 Get started by creating your first flow, logic app, or function app. Select any of the following links:
 
-* [Get started with Microsoft Flow](/power-automate/getting-started)
+* [Get started with Power Automate](/power-automate/getting-started)
 * [Create a logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md)
 * [Create your first Azure function](functions-create-first-azure-function.md)

articles/cognitive-services/Anomaly-Detector/How-to/deploy-anomaly-detection-on-container-instances.md

@@ -3,13 +3,13 @@ title: Run Anomaly Detector Container in Azure Container Instances
 titleSuffix: Azure Cognitive Services
 description: Deploy the Anomaly Detector container to an Azure Container Instance, and test it in a web browser.
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: anomaly-detector
 ms.topic: conceptual
-ms.date: 01/23/2020
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ---
 
 # Deploy an Anomaly Detector container to Azure Container Instances

articles/cognitive-services/Anomaly-Detector/anomaly-detector-container-configuration.md

@@ -3,13 +3,13 @@ title: How to configure a container for Anomaly Detector API
 titleSuffix: Azure Cognitive Services
 description: The Anomaly Detector API container runtime environment is configured using the `docker run` command arguments. This container has several required settings, along with a few optional settings. 
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: anomaly-detector
 ms.topic: conceptual
-ms.date: 11/07/2019
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ---
 
 # Configure Anomaly Detector containers

articles/cognitive-services/Anomaly-Detector/anomaly-detector-container-howto.md

@@ -3,13 +3,13 @@ title: How to install and run containers for using Anomaly Detector API
 titleSuffix: Azure Cognitive Services
 description: Use the Anomaly Detector API's advanced algorithms to identify anomalies in your time series data.
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: anomaly-detector
 ms.topic: conceptual
-ms.date: 11/21/2019
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ---
 
 # Install and run Anomaly Detector containers (Preview)

articles/cognitive-services/Anomaly-Detector/includes/create-anomaly-detector-resource.md

@@ -2,12 +2,12 @@
 title: Container support
 titleSuffix: Azure Cognitive Services
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.topic: include 
-ms.date: 7/5/2019
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ---
 
 ## Create an Anomaly Detector resource

articles/cognitive-services/Computer-vision/computer-vision-how-to-install-containers.md

@@ -3,13 +3,13 @@ title: How to install and run containers - Computer Vision
 titleSuffix: Azure Cognitive Services
 description: How to download, install, and run containers for Computer Vision in this walkthrough tutorial.
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: computer-vision
 ms.topic: conceptual
-ms.date: 03/17/2020
-ms.author: pafarley
+ms.date: 04/01/2020
+ms.author: aahi
 ms.custom: seodec18
 ---
 

articles/cognitive-services/Computer-vision/computer-vision-resource-container-config.md

@@ -3,13 +3,13 @@ title: Configure containers - Computer Vision
 titleSuffix: Azure Cognitive Services
 description: This article shows you how to configure both required and optional settings for Recognize Text containers in Computer Vision.
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: computer-vision
 ms.topic: conceptual
-ms.date: 11/04/2019
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ms.custom: seodec18
 ---
 

articles/cognitive-services/Computer-vision/deploy-computer-vision-on-container-instances.md

@@ -3,13 +3,13 @@ title: Run Computer Vision container in Azure Container Instances
 titleSuffix: Azure Cognitive Services
 description: Deploy the Computer Vision container to an Azure Container Instance, and test it in a web browser.
 services: cognitive-services
-author: IEvangelist
+author: aahill
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: computer-vision
 ms.topic: conceptual
-ms.date: 11/04/2019
-ms.author: dapine
+ms.date: 04/01/2020
+ms.author: aahi
 ---
 
 # Deploy the Computer Vision container to Azure Container Instances