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

Author: tamram

articles/active-directory/conditional-access/media/block-legacy-authentication/01.png

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: identity-protection
 ms.topic: conceptual
-ms.date: 10/18/2019
+ms.date: 05/05/2020
 
 ms.author: joflore
 author: MicrosoftGuyJFlo
@@ -47,12 +47,11 @@ Configure the users at risk email in the **Azure portal** under **Azure Active D
 The weekly digest email contains a summary of new risk detections.  
 It includes:
 
-- Users at risk
-- Suspicious activities
-- Detected vulnerabilities
+- New risky users detected
+- New risky sign-ins detected (in real-time)
 - Links to the related reports in Identity Protection
 
-![Weekly digest email](./media/howto-identity-protection-configure-notifications/400.png)
+![Weekly digest email](./media/howto-identity-protection-configure-notifications/weekly-digest-email.png)
 
 By default, recipients include all Global Admins. Global Admins can also add other Global Admins, Security Admins, Security Readers as recipients.
 

articles/active-directory/identity-protection/howto-identity-protection-configure-notifications.md

@@ -4,7 +4,7 @@ description: This article provides answers to some of the more common questions
 author: minewiskan
 ms.service: azure-analysis-services
 ms.topic: conceptual
-ms.date: 04/29/2020
+ms.date: 05/05/2020
 ms.author: owend
 ms.reviewer: minewiskan
 ---
@@ -19,7 +19,11 @@ This article provides answers to common questions about connecting to storage ac
 **Answer** - Azure Analysis Services does not use fixed IP addresses or Service Tags. The range of IP addresses your Analysis Services servers use can be anything in the range of IP addresses for the *Azure region*. Because your server IP addresses are variable and can change over time, your firewall rules need to allow for the entire range of Azure region IP addresses your server is in.
 
 **Question** - My Azure storage account is in a different region from my Analysis Services server. How do I configure storage account firewall settings?   
-**Answer** - If the storage account is in a different region, firewall settings must be configured to allow access from **All networks**. Firewall settings configured for Selected networks with whitelisted IP addresses and Allow trusted Microsoft services exception is not supported.
+**Answer** - If the storage account is in a different region, configure storage account firewall settings to allow access from **Selected networks**. In Firewall **Address range**, specify the IP address range for the region the Analysis Services server is in. To get the IP ranges for Azure regions, see [Azure IP Ranges and Service Tags – Public Cloud](https://www.microsoft.com/download/details.aspx?id=56519). Configuring storage account firewall settings to allow access from All networks is supported, however choosing Selected networks and specifying an IP address range is preferred. 
+
+**Question** - My Azure storage account is in the same region as my Analysis Services server. How can I configure storage account firewall settings?   
+**Answer** – Because your Analysis Services server and storage account are in the same region, communications between them use internal IP address ranges, therefore, configuring a firewall to use Selected networks and specifying an IP address range is not supported. If organization policies require a firewall, it must be configured to allow access from All networks.
+
 
 ## Data source connections
 

articles/active-directory/identity-protection/media/howto-identity-protection-configure-notifications/400.png

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting the onboarding of Azure Automation management solutions
-description: Learn how to troubleshoot solution onboarding errors.
+description: Learn how to troubleshoot Azure Automation solution onboarding errors.
 services: automation
 author: mgoedtel
 ms.author: magoedte
@@ -11,43 +11,41 @@ manager: carmonm
 ---
 # Troubleshoot solution onboarding
 
-You might receive errors when onboarding the Update Management solution or the Change Tracking and Inventory solution. This article describes the various errors that might occur and how to resolve them.
+You might receive error messages when you onboard the Azure Automation Update Management solution or the Change Tracking and Inventory solution. This article describes the various errors that might occur and how to resolve them.
 
 ## Known issues
 
 ### <a name="node-rename"></a>Scenario: Renaming a registered node requires unregister or register again
 
 #### Issue
 
-A node is registered to Azure Automation and then the operating system computer name is changed. Reports from the node
-continue to appear with the original name.
+A node is registered to Azure Automation, and then the operating system computer name is changed. Reports from the node continue to appear with the original name.
 
 #### Cause
 
-Renaming registered nodes does not update the node name in Azure Automation.
+Renaming registered nodes doesn't update the node name in Azure Automation.
 
 #### Resolution
 
-Unregister the node from Azure Automation State Configuration and then register it again. Reports published to the 
-service before that time will no longer be available.
+Unregister the node from Azure Automation State Configuration, and then register it again. Reports published to the service before that time will no longer be available.
 
-### <a name="resigning-cert"></a>Scenario: Re-signing certificates via https proxy is not supported
+### <a name="resigning-cert"></a>Scenario: Re-signing certificates via HTTPS proxy isn't supported
 
 #### Issue
 
-When connecting through a proxy solution that terminates HTTPS traffic and then re-encrypts the traffic using a new certificate, the service does not allow the connection.
+When you connect through a proxy solution that terminates HTTPS traffic and then re-encrypts the traffic using a new certificate, the service doesn't allow the connection.
 
 #### Cause
 
-Azure Automation does not support re-signing certificates used to encrypt traffic.
+Azure Automation doesn't support re-signing certificates used to encrypt traffic.
 
 #### Resolution
 
-There is currently no workaround for this issue.
+There's currently no workaround for this issue.
 
 ## General errors
 
-### <a name="missing-write-permissions"></a>Scenario: Onboarding fails with the message - The solution cannot be enabled
+### <a name="missing-write-permissions"></a>Scenario: Onboarding fails with the message "The solution cannot be enabled"
 
 #### Issue
 
@@ -67,9 +65,9 @@ This error is caused by incorrect or missing permissions on the VM or workspace,
 
 #### Resolution
 
-Ensure that you have correct [permissions needed to onboard machines](../automation-role-based-access-control.md#onboarding-permissions) and then try to onboard the solution again. If you receive the error `The solution cannot be enabled on this VM because the permission to read the workspace is missing`, ensure that you have the `Microsoft.OperationalInsights/workspaces/read` permission to be able to find if the VM is onboarded to a workspace.
+Ensure that you have correct [permissions needed to onboard machines](../automation-role-based-access-control.md#onboarding-permissions), and then try to onboard the solution again. If you receive the error message `The solution cannot be enabled on this VM because the permission to read the workspace is missing`, ensure that you have the `Microsoft.OperationalInsights/workspaces/read` permission to be able to find if the VM is onboarded to a workspace.
 
-### <a name="diagnostic-logging"></a>Scenario: Onboarding fails with the message: Failed to configure automation account for diagnostic logging
+### <a name="diagnostic-logging"></a>Scenario: Onboarding fails with the message "Failed to configure automation account for diagnostic logging"
 
 #### Issue
 
@@ -81,25 +79,25 @@ Failed to configure automation account for diagnostic logging
 
 #### Cause
 
-This error can be caused if the pricing tier doesn't match the subscription's billing model. See [Monitoring usage and estimated costs in Azure Monitor](https://aka.ms/PricingTierWarning).
+This error can be caused if the pricing tier doesn't match the subscription's billing model. For more information, see [Monitoring usage and estimated costs in Azure Monitor](https://aka.ms/PricingTierWarning).
 
 #### Resolution
 
-Create your Log Analytics workspace manually and repeat the onboarding process to select the workspace created.
+Create your Log Analytics workspace manually, and repeat the onboarding process to select the workspace created.
 
 ### <a name="computer-group-query-format-error"></a>Scenario: ComputerGroupQueryFormatError
 
 #### Issue
 
-This error code means that the saved search computer group query used to target the solution is not formatted correctly. 
+This error code means that the saved search computer group query used to target the solution isn't formatted correctly. 
 
 #### Cause
 
 You might have altered the query, or the system might have altered it.
 
 #### Resolution
 
-You can delete the query for the solution and then onboard the solution again, which recreates the query. The query can be found in your workspace, under **Saved searches**. The name of the query is **MicrosoftDefaultComputerGroup**, and the category of the query is the name of the associated solution. If multiple solutions are enabled, the **MicrosoftDefaultComputerGroup** query shows multiple times under **Saved Searches**.
+You can delete the query for the solution and then onboard the solution again, which re-creates the query. The query can be found in your workspace under **Saved searches**. The name of the query is **MicrosoftDefaultComputerGroup**, and the category of the query is the name of the associated solution. If multiple solutions are enabled, the **MicrosoftDefaultComputerGroup** query shows multiple times under **Saved searches**.
 
 ### <a name="policy-violation"></a>Scenario: PolicyViolation
 
@@ -113,20 +111,20 @@ A policy is blocking the operation from completing.
 
 #### Resolution
 
-In order to successfully deploy the solution, you must consider altering the indicated policy. As there are many different types of policies that can be defined, the changes required depend on the policy that is violated. For example, if a policy is defined on a resource group that denies permission to change the contents of some contained resources, you might choose one of these fixes:
+To successfully deploy the solution, you must consider altering the indicated policy. Because there are many different types of policies that can be defined, the changes required depend on the policy that's violated. For example, if a policy is defined on a resource group that denies permission to change the contents of some contained resources, you might choose one of these fixes:
 
 * Remove the policy altogether.
 * Try to onboard the solution to a different resource group.
-* Re-target the policy to a specific resource, for example, an Automation account.
+* Retarget the policy to a specific resource, for example, an Automation account.
 * Revise the set of resources that the policy is configured to deny.
 
-Check the notifications in the top right corner of the Azure portal or navigate to the resource group that contains your Automation account and select **Deployments** under **Settings** to view the failed deployment. To learn more about Azure Policy, see [Overview of Azure Policy](../../governance/policy/overview.md?toc=%2fazure%2fautomation%2ftoc.json).
+Check the notifications in the upper-right corner of the Azure portal, or go to the resource group that contains your Automation account and select **Deployments** under **Settings** to view the failed deployment. To learn more about Azure Policy, see [Overview of Azure Policy](../../governance/policy/overview.md?toc=%2fazure%2fautomation%2ftoc.json).
 
 ### <a name="unlink"></a>Scenario: Errors trying to unlink a workspace
 
 #### Issue
 
-You receive the following error when trying to unlink a workspace:
+You receive the following error message when you try to unlink a workspace:
 
 ```error
 The link cannot be updated or deleted because it is linked to Update Management and/or ChangeTracking Solutions.
@@ -138,16 +136,16 @@ This error occurs when you still have solutions active in your Log Analytics wor
 
 ### Resolution
 
-Remove the following solutions from your workspace if you are using them:
+Remove the following solutions from your workspace if you're using them:
 
 * Update Management
 * Change Tracking and Inventory
 * Start/Stop VMs during off-hours
 
-Once you remove the solutions, you can unlink your workspace. It's important to clean up any existing artifacts from these solutions from your workspace and your Automation account 
+After you remove the solutions, you can unlink your workspace. It's important to clean up any existing artifacts from these solutions from your workspace and your Automation account:
 
-* For Update Management, remove Update Deployments (Schedules) from your Automation account.
-* For Start/Stop VMs during off-hours, remove any locks on solution components in your Automation account under **Settings** > **Locks**. See [Remove the Start/Stop VMs during off-hours solution](../automation-solution-vm-management.md#remove-the-solution).
+* For Update Management, remove **Update Deployments (Schedules)** from your Automation account.
+* For Start/Stop VMs during off-hours, remove any locks on solution components in your Automation account under **Settings** > **Locks**. For more information, see [Remove the Start/Stop VMs during off-hours solution](../automation-solution-vm-management.md#remove-the-solution).
 
 ## <a name="mma-extension-failures"></a>Log Analytics for Windows extension failures
 
@@ -176,22 +174,22 @@ Please verify the VM has a running VM agent, and can establish outbound connecti
 
 #### Cause
 
-Some potential causes to this error are:
+Some potential causes of this error are:
 
 * A proxy configured in the VM only allows specific ports.
 * A firewall setting has blocked access to the required ports and addresses.
 
 #### Resolution
 
-Ensure that you have the proper ports and addresses open for communication. For a list of ports and addresses, see [planning your network](../automation-hybrid-runbook-worker.md#network-planning).
+Ensure that you have the proper ports and addresses open for communication. For a list of ports and addresses, see [Planning your network](../automation-hybrid-runbook-worker.md#network-planning).
 
-### <a name="transient-environment-issue"></a>Scenario: Install failed because of a transient environment issues
+### <a name="transient-environment-issue"></a>Scenario: Install failed because of transient environment issues
 
-The installation of the Log Analytics for Windows extension failed during deployment because of another installation or action blocking the installation
+The installation of the Log Analytics for Windows extension failed during deployment because of another installation or action blocking the installation.
 
 #### Issue
 
-The following are examples of error messages may be returned:
+The following are examples of error messages that might be returned:
 
 ```error
 The Microsoft Monitoring Agent failed to install on this machine. Please try to uninstall and reinstall the extension. If the issue persists, please contact support.
@@ -207,7 +205,7 @@ The Microsoft Monitoring Agent failed to install on this machine. Please try to
 
 #### Cause
 
-Some potential causes to this error are:
+Some potential causes of this error are:
 
 * Another installation is in progress.
 * The system is triggered to reboot during template deployment.
@@ -238,8 +236,8 @@ Try to install the Log Analytics agent for Windows extension when the VM is unde
 
 ## Next steps
 
-If you don't see your problem above or can't resolve your issue, try one of the following channels for additional support:
+If you don't see your problem here or you can't resolve your issue, try one of the following channels for additional support:
 
 * Get answers from Azure experts through [Azure Forums](https://azure.microsoft.com/support/forums/).
-* Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience by connecting the Azure community to the right resources: answers, support, and experts.
-* File an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.
+* Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
+* File an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/), and select **Get Support**.