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

Author: TimShererWithAquent

articles/active-directory/reports-monitoring/concept-audit-logs.md

@@ -38,11 +38,11 @@ This article gives you an overview of the audit report.
 
 ## Who can access the data?
 
-* Users in the **Security Administrator**, **Security Reader**, **Report Reader** or **Global Administrator** roles
+* Users in the **Security Administrator**, **Security Reader**, **Report Reader** , **Global Reader** or **Global Administrator** roles
 
 ## Audit logs
 
-The Azure AD audit logs provide records of system activities for compliance. To access the audit report, select **Audit logs** in the **Activity** section of **Azure Active Directory**. Note that audit logs may have a latency of up to an hour, so it may take that long for audit activity data to show up in the portal after you have completed the task.
+The Azure AD audit logs provide records of system activities for compliance. To access the audit report, select **Audit logs** in the **Monitoring** section of **Azure Active Directory**. Note that audit logs may have a latency of up to an hour, so it may take that long for audit activity data to show up in the portal after you have completed the task.
 
 
 
@@ -87,16 +87,20 @@ You can filter the audit data on the following fields:
 The **Service** filter allows you to select from a drop-down list of the following services:
 
 - All
+- AAD Management UX
 - Access Reviews
-- Account Provisioning 
-- Application SSO
+- Account Provisioning
+- Application Proxy
 - Authentication Methods
 - B2C
 - Conditional Access
 - Core Directory
 - Entitlement Management
+- Hybrid Authentication
 - Identity Protection
 - Invited Users
+- MIM Service
+- MyApps
 - PIM
 - Self-service Group Management
 - Self-service Password Management
@@ -115,7 +119,11 @@ The **Category** filter enables you to select one of the following filters:
 - DirectoryManagement
 - EntitlementManagement
 - GroupManagement
+- KerberosDomain
+- KeyManagement
+- Label
 - Other
+- PermissionGrantPolicy
 - Policy
 - ResourceManagement
 - RoleManagement
@@ -131,14 +139,13 @@ The **Status** filter allows you to filter based on the status of an audit opera
 - Success
 - Failure
 
-The **Target** filter allows you to search for a particular target by name or user principal name (UPN). The target name and UPN are case-sensitive. 
+The **Target** filter allows you to search for a particular target by the starting of the name or user principal name (UPN). The target name and UPN are case-sensitive. 
 
-The **Initiated by** filter enables you to define an actor's name or a universal principal name (UPN). The name and UPN are case-sensitive.
+The **Initiated by** filter enables you to define what an actor's name or a universal principal name (UPN) starts with. The name and UPN are case-sensitive.
 
 The **Date range** filter enables to you to define a timeframe for the returned data.  
 Possible values are:
 
-- 1 month
 - 7 days
 - 24 hours
 - Custom
@@ -176,11 +183,11 @@ With user and group-based audit reports, you can get answers to questions such a
 
 - What licenses have been assigned to a group or a user?
 
-If you want to review only auditing data that is related to users, you can find a filtered view under **Audit logs** in the **Activity** section of the **Users** tab. This entry point has **UserManagement** as preselected category.
+If you want to review only auditing data that is related to users, you can find a filtered view under **Audit logs** in the **Monitoring** section of the **Users** tab. This entry point has **UserManagement** as preselected category.
 
 ![Audit logs](./media/concept-audit-logs/users.png "Audit logs")
 
-If you want to review only auditing data that is related to groups, you can find a filtered view under **Audit logs** in the **Activity** section of the **Groups** tab. This entry point has **GroupManagement** as preselected category.
+If you want to review only auditing data that is related to groups, you can find a filtered view under **Audit logs** in the **Monitoring** section of the **Groups** tab. This entry point has **GroupManagement** as preselected category.
 
 ![Audit logs](./media/concept-audit-logs/groups.png "Audit logs")
 

articles/azure-functions/functions-how-to-azure-devops.md

@@ -1,11 +1,11 @@
 ---
 title: Continuously update function app code using Azure DevOps
 description: Learn how to set up an Azure DevOps pipeline that targets Azure Functions.
-author: ahmedelnably
+author: craigshoemaker
 
 ms.topic: conceptual
 ms.date: 04/18/2019
-ms.author: aelnably
+ms.author: cshoe
 ---
 
 # Continuous delivery by using Azure DevOps

articles/azure-functions/functions-how-to-github-actions.md

@@ -1,10 +1,10 @@
 ---
 title: Use GitHub Actions to make code updates in Azure Functions
 description: Learn how to use GitHub Actions to define a workflow to build and deploy Azure Functions projects in GitHub.
-author: ahmedelnably
+author: craigshoemaker
 ms.topic: conceptual
 ms.date: 09/16/2019
-ms.author: aelnably
+ms.author: cshoe
 ---
 
 # Continuous delivery by using GitHub Action

articles/azure-functions/functions-monitor-log-analytics.md

@@ -1,10 +1,10 @@
 ---
 title: Monitoring Azure Functions with Azure Monitor Logs
 description: Learn how to use Azure Monitor Logs with Azure Functions to monitor function executions.
-author: ahmedelnably
+author: craigshoemaker
 ms.topic: conceptual
 ms.date: 10/09/2019
-ms.author: aelnably
+ms.author: cshoe
 # Customer intent: As a developer, I want to monitor my functions so I can know if they're running correctly.
 ---
 

articles/azure-monitor/log-query/query-optimization.md

@@ -34,11 +34,11 @@ The following query performance indicators are available for every query that is
 
 - [Total CPU](#total-cpu): Overall compute used to process the query across all compute nodes. It represents time used for computing, parsing, and data fetching. 
 
-- [Data volume](#data-volume): Overall data that was accessed to process the query. Influenced by the size of the target table, time span used, filters applied, and the number of columns referenced.
+- [Data used for processed query](#data-used-for-processed-query): Overall data that was accessed to process the query. Influenced by the size of the target table, time span used, filters applied, and the number of columns referenced.
 
-- [Time range](#time-range): The gap between the newest and the oldest data that was accessed to process the query. Influenced by the explicit time range specified for the query.
+- [Time span of the processed query](#time-span-of-the-processed-query): The gap between the newest and the oldest data that was accessed to process the query. Influenced by the explicit time range specified for the query.
 
-- [Age of data](#age-of-data): The gap between now and the oldest data that was accessed to process the query. It highly influences the efficiency of data fetching.
+- [Age of processed data](#age-of-processed-data): The gap between now and the oldest data that was accessed to process the query. It highly influences the efficiency of data fetching.
 
 - [Number of workspaces](#number-of-workspaces): How many workspaces were accessed during the query processing due to implicit or explicit selection.
 
@@ -147,7 +147,7 @@ Heartbeat
 > This indicator presents only CPU from the immediate cluster. In multi-region query, it would represent only one of the regions. In multi-workspace query, it might not include all workspaces.
 
 
-## Data volume
+## Data used for processed query
 
 A critical factor in the processing of the query is the volume of data that is scanned and used for the query processing. Azure Data Explorer uses aggressive optimizations that dramatically reduce the data volume compared to other data platforms. Still, there are critical factors in the query that can impact the data volume that is used.
 In Azure Monitor Logs, the **TimeGenerated** column is used as a way to index the data. Restricting the **TimeGenerated** values to as narrow a range as possible will make a significant improvement to query performance by significantly limiting the amount of data that has to be processed.
@@ -205,7 +205,7 @@ SecurityEvent
 | summarize count(), dcount(EventID), avg(Level) by Computer  
 ```
 
-## Time range
+## Time span of the processed query
 
 All logs in Azure Monitor Logs are partitioned according to the **TimeGenerated** column. The number of partitions that are accessed are directly related to the time span. Reducing the time range is the most efficient way of assuring a prompt query execution.
 
@@ -258,7 +258,7 @@ by Computer
 > [!IMPORTANT]
 > This indicator isn't available for cross region queries.
 
-## Age of data
+## Age of processed data
 Azure Data Explorer uses several storage tiers: in-memory, local SSD disks and much slower Azure Blobs. The newer the data, the higher is the chance that it is stored in a more performant tier with smaller latency, reducing the query duration and CPU. Other than the data itself, the system also has a cache for metadata. The older the data, the less chance its metadata will be in cache.
 
 While some queries require usage of old data, there are cases where old data is used by mistake. This happens when queries are executed without providing time range in their meta-data and not all table references include filter on the **TimeGenerated** column. In these cases, the system will scan all the data that is stored in that table. When the data retention is long, it can cover long time ranges and thus data that is as old as the data retention period.

articles/batch/TOC.yml

@@ -123,6 +123,8 @@
       href: large-number-tasks.md
     - name: Check for job and task errors
       href: batch-job-task-error-checking.md
+    - name: Detecting and handling Batch service errors
+      href: batch-retry-after-errors.md   
   - name: Create resource files
     href: resource-files.md
   - name: Persist job and task output

articles/batch/batch-retry-after-errors.md

@@ -0,0 +1,39 @@
+---
+title: Retrying tasks after an error
+description: Check for errors and retry them.
+services: batch
+documentationcenter: .net
+author: LauraBrenner
+manager: evansma
+editor: ''
+tags: azure-batch
+
+ms.assetid: 16279b23-60ff-4b16-b308-5de000e4c028
+ms.service: batch
+ms.topic: article
+ms.tgt_pltfrm: 
+ms.workload: big-compute
+ms.date: 02/15/2020
+ms.author: labrenne
+ms.custom: seodec18
+---
+
+# Detecting and handling Batch service errors
+
+It is important to remember to check for errors when working with a REST service API. It isn't uncommon for errors to occur when running batch jobs.
+
+## Common errors 
+
+- Networking failures - these are requests that never reached Batch or the Batch response didn't reach the client in time.
+- Internal server errors - these are standard 5xx status code HTTP response.
+- Throttling can cause errors such as 429 or 503 status code HTTP responses with the Retry-after header.
+- 4xx errors that include such errors as AlreadyExists and InvalidOperation. This means that the resource is not in the correct state for the state transition.
+
+## When to retry
+
+The Batch APIs will notify you if there is a failure. They can all be retried, and they all include a global retry handler for that purpose. It is best to use this built-in mechanism.
+
+After a failure, you should wait a bit (several seconds between retries) before retrying. If you retry too frequently or too quickly, the retry handler will throttle.
+
+
+For detailed information about each API and their default retry policies, read [Batch Status and Error Codes](https://docs.microsoft.com/rest/api/batchservice/batch-status-and-error-codes).

articles/cost-management-billing/costs/quick-acm-cost-analysis.md

@@ -44,7 +44,7 @@ The initial cost analysis view includes the following areas.
 
 **Actual cost**: Shows the total usage and purchase costs for the current month, as they're accrued and will show on your bill.
 
-**Forecast**: Shows the total forecasted costs for time period you choose. (Forecast is in preview.)
+**Forecast**: Shows the total forecasted costs for time period you choose.
 
 **Budget**: Shows the planned spending limit for the selected scope, if available.
 

articles/dms/dms-overview.md

@@ -3,13 +3,13 @@ title: What is Azure Database Migration Service?
 description: Overview of Azure Database Migration Service, which provides seamless migrations from many database sources to Azure Data platforms.
 services: database-migration
 author: pochiraju
-ms.author: jtoland
+ms.author: rajpo
 manager: craigg
 ms.reviewer: craigg
 ms.service: dms
 ms.workload: data-services
 ms.topic: article
-ms.date: 06/01/2019
+ms.date: 02/20/2020
 ---
 # What is Azure Database Migration Service?
 

articles/dms/dms-tools-matrix.md

@@ -2,15 +2,15 @@
 title: Azure Database Migration Service tools matrix
 description: Learn about the services and tools available to migrate databases and to support various phases of the migration process.
 services: database-migration
-author: HJToland3
-ms.author: jtoland
+author: pochiraju
+ms.author: rajpo
 manager: craigg
 ms.reviewer: craigg
 ms.service: dms
 ms.workload: data-services
 ms.custom: mvc
 ms.topic: article
-ms.date: 01/10/2020
+ms.date: 02/20/2020
 ---
 
 # Services and tools available for data migration scenarios