Merge pull request #220118 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit b13509b30a68 · 2022-12-01T14:39:22.000-08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->
diff --git a/articles/active-directory/fundamentals/whats-new-archive.md b/articles/active-directory/fundamentals/whats-new-archive.md
@@ -8597,13 +8597,13 @@ For more information about how to use these reports, see [Azure Active Directory
 
 ---
 
-### Use "Report Reader" role (non-admin role) to view Azure AD Activity Reports
+### Use "Reports Reader" role (non-admin role) to view Azure AD Activity Reports
 
 **Type:** New feature
 **Service category:** Reporting
 **Product capability:** Monitoring & Reporting
 
-As part of customers feedback to enable non-admin roles to have access to Azure AD activity logs, we've enabled the ability for users who are in the "Report Reader" role to access Sign-ins and Audit activity within the Azure portal as well as using the Microsoft Graph API.
+As part of customers feedback to enable non-admin roles to have access to Azure AD activity logs, we've enabled the ability for users who are in the "Reports Reader" role to access Sign-ins and Audit activity within the Azure portal as well as using the Microsoft Graph API.
 
 For more information, how to use these reports, see [Azure Active Directory reporting](../reports-monitoring/overview-reports.md).
 
diff --git a/articles/active-directory/governance/entitlement-management-logs-and-reporting.md b/articles/active-directory/governance/entitlement-management-logs-and-reporting.md
@@ -60,7 +60,7 @@ To view events for an access package, you must have access to the underlying Azu
 - Global administrator  
 - Security administrator  
 - Security reader  
-- Report reader  
+- Reports reader  
 - Application administrator  
 
 Use the following procedure to view events: 
diff --git a/articles/active-directory/hybrid/how-to-connect-health-adfs-risky-ip-workbook.md b/articles/active-directory/hybrid/how-to-connect-health-adfs-risky-ip-workbook.md
@@ -37,7 +37,7 @@ Additionally, it is possible for a single IP address to attempt multiple logins
 2.	A Log Analytics Workspace with the “ADFSSignInLogs” stream enabled.
 3.	Permissions to use the Azure AD Monitor Workbooks. To use Workbooks, you need:
 - An Azure Active Directory tenant with a premium (P1 or P2) license.
-- Access to a Log Analytics Workspace and the following roles in Azure AD (if accessing Log Analytics through Azure AD portal): Security administrator, Security reader, Report reader, Global administrator
+- Access to a Log Analytics Workspace and the following roles in Azure AD (if accessing Log Analytics through Azure AD portal): Security administrator, Security reader, Reports reader, Global administrator
 
 
 ## What is in the report?
diff --git a/articles/active-directory/manage-apps/migrate-adfs-application-activity.md b/articles/active-directory/manage-apps/migrate-adfs-application-activity.md
@@ -25,7 +25,7 @@ The AD FS application activity report in the Azure portal lets you quickly ident
 * **Prioritize applications for migration.** Get the number of unique users who have signed in to the application in the past 1, 7, or 30 days to help determine the criticality or risk of migrating the application.
 * **Run migration tests and fix issues.** The reporting service automatically runs tests to determine if an application is ready to migrate. The results are displayed in the AD FS application activity report as a migration status. If the AD FS configuration is not compatible with an Azure AD configuration, you get specific guidance on how to address the configuration in Azure AD.
 
-The AD FS application activity data is available to users who are assigned any of these admin roles: global administrator, report reader, security reader, application administrator, or cloud application administrator.
+The AD FS application activity data is available to users who are assigned any of these admin roles: global administrator, reports reader, security reader, application administrator, or cloud application administrator.
 
 ## Prerequisites
 
@@ -42,7 +42,7 @@ The AD FS application activity data is available to users who are assigned any o
 
 The AD FS application activity report is available in the Azure portal under Azure AD **Usage & insights** reporting. The AD FS application activity report analyzes each AD FS application to determine if it can be migrated as-is, or if additional review is needed.
 
-1. Sign in to the [Azure portal](https://portal.azure.com) with an admin role that has access to AD FS application activity data (global administrator, report reader, security reader, application administrator, or cloud application administrator).
+1. Sign in to the [Azure portal](https://portal.azure.com) with an admin role that has access to AD FS application activity data (global administrator, reports reader, security reader, application administrator, or cloud application administrator).
 
 2. Select **Azure Active Directory**, and then select **Enterprise applications**.
 
diff --git a/articles/active-directory/reports-monitoring/concept-audit-logs.md b/articles/active-directory/reports-monitoring/concept-audit-logs.md
@@ -68,7 +68,7 @@ With an application-centric view, you can get answers to questions such as:
 
 The audit activity report is available in all editions of Azure AD. To access the audit logs, you need to have one of the following roles: 
 
-- Report Reader
+- Reports Reader
 - Security Reader
 - Security Administrator
 - Global Reader
diff --git a/articles/active-directory/reports-monitoring/concept-provisioning-logs.md b/articles/active-directory/reports-monitoring/concept-provisioning-logs.md
@@ -42,7 +42,7 @@ To view the provisioning logs, your tenant must have an Azure AD Premium license
 
 Application owners can view logs for their own applications. The following roles are required to view provisioning logs:
 
-- Report Reader
+- Reports Reader
 - Security Reader
 - Security Operator
 - Security Administrator
diff --git a/articles/active-directory/reports-monitoring/concept-usage-insights-report.md b/articles/active-directory/reports-monitoring/concept-usage-insights-report.md
@@ -29,7 +29,7 @@ Accessing the data from Usage and insights requires:
 
 * An Azure AD tenant
 * An Azure AD premium (P1/P2) license to view the sign-in data
-* A user in the Global Administrator, Security Administrator, Security Reader, or Report Reader roles.
+* A user in the Global Administrator, Security Administrator, Security Reader, or Reports Reader roles.
 
 To access Usage & insights:
 
diff --git a/articles/active-directory/reports-monitoring/howto-analyze-activity-logs-log-analytics.md b/articles/active-directory/reports-monitoring/howto-analyze-activity-logs-log-analytics.md
@@ -33,7 +33,7 @@ To follow along, you need:
 * The following roles in Azure Active Directory (if you're accessing Log Analytics through Azure Active Directory portal)
     - Security Admin
     - Security Reader
-    - Report Reader
+    - Reports Reader
     - Global Admin
     
 ## Navigate to the Log Analytics workspace
diff --git a/articles/active-directory/reports-monitoring/howto-configure-prerequisites-for-reporting-api.md b/articles/active-directory/reports-monitoring/howto-configure-prerequisites-for-reporting-api.md
@@ -215,7 +215,7 @@ Accessing sign-in reports requires an Azure Active Directory premium 1 (P1) lice
 
 ### Error: The allowed roles doesn't include User. 
 
- Avoid errors trying to access audit logs or sign-in using the API. Make sure your account is part of the **Security Reader** or **Report Reader** role in your Azure Active Directory tenant.
+ Avoid errors trying to access audit logs or sign-in using the API. Make sure your account is part of the **Security Reader** or **Reports Reader** role in your Azure Active Directory tenant.
 
 ### Error: Application missing Azure AD 'Read directory data' permission 
 
diff --git a/articles/active-directory/reports-monitoring/howto-download-logs.md b/articles/active-directory/reports-monitoring/howto-download-logs.md
@@ -60,7 +60,7 @@ You can also download activity logs using Microsoft Graph; however, downloading
 
 While the global administrator works, you should use an account with lower privileges to perform this task. To access the audit logs, the following roles work:
 
-- Report Reader
+- Reports Reader
 - Global Reader
 - Security Administrator
 - Security Reader
diff --git a/articles/active-directory/reports-monitoring/howto-troubleshoot-sign-in-errors.md b/articles/active-directory/reports-monitoring/howto-troubleshoot-sign-in-errors.md
@@ -32,7 +32,7 @@ In addition, the sign-ins report can also help you troubleshoot sign-in failures
 You need:
 
 * An Azure AD tenant with a premium (P1/P2) license. See [Getting started with Azure Active Directory Premium](../fundamentals/active-directory-get-started-premium.md) to upgrade your Azure Active Directory edition.
-* A user, who is in the **global administrator**, **security administrator**, **security reader**, or **report reader** role for the tenant. In addition, any user can access their own sign-ins. 
+* A user, who is in the **global administrator**, **security administrator**, **security reader**, or **reports reader** role for the tenant. In addition, any user can access their own sign-ins. 
 
 ## Troubleshoot sign-in errors using the sign-ins report
 
diff --git a/articles/active-directory/reports-monitoring/howto-use-azure-monitor-workbooks.md b/articles/active-directory/reports-monitoring/howto-use-azure-monitor-workbooks.md
@@ -105,7 +105,7 @@ To use Monitor workbooks, you need:
 - Following roles in Azure Active Directory (if you're accessing Log Analytics through Azure Active Directory portal)
     - Security administrator
     - Security reader
-    - Report reader
+    - Reports reader
     - Global administrator
 
 ## Roles
diff --git a/articles/active-directory/reports-monitoring/plan-monitoring-and-reporting.md b/articles/active-directory/reports-monitoring/plan-monitoring-and-reporting.md
@@ -147,7 +147,7 @@ The following roles can read Azure AD reports:
 
 * Security Reader
 
-* Report Reader
+* Reports Reader
 
 Learn More About [Azure AD Administrative Roles](../roles/permissions-reference.md).
 
diff --git a/articles/active-directory/reports-monitoring/troubleshoot-graph-api.md b/articles/active-directory/reports-monitoring/troubleshoot-graph-api.md
@@ -30,7 +30,7 @@ Accessing sign-in reports requires an Azure Active Directory premium 1 (P1) lice
 
 ### Error: User isn't in the allowed roles 
 
-If you see this error message while trying to access audit logs or sign-ins using the API, make sure that your account is part of the **Security Reader** or **Report Reader** role in your Azure Active Directory tenant. 
+If you see this error message while trying to access audit logs or sign-ins using the API, make sure that your account is part of the **Security Reader** or **Reports Reader** role in your Azure Active Directory tenant. 
 
 ### Error: Application missing Azure AD 'Read directory data' permission 
 
diff --git a/articles/active-directory/reports-monitoring/tutorial-access-api-with-certificates.md b/articles/active-directory/reports-monitoring/tutorial-access-api-with-certificates.md
@@ -28,7 +28,7 @@ In this tutorial, you learn how to use a test certificate to access the MS Graph
 
 1. To access sign-in data, make sure you have an Azure AD tenant with a premium (P1/P2) license. See [Getting started with Azure Active Directory Premium](../fundamentals/active-directory-get-started-premium.md) to upgrade your Azure AD edition. If you didn't have any activities data prior to the upgrade, it will take a couple of days for the data to show up in the reports after you upgrade to a premium license. 
 
-2. Create or switch to a user account in the **Global Administrator**, **Security Administrator**, **Security Reader** or **Report Reader** role for the tenant. 
+2. Create or switch to a user account in the **Global Administrator**, **Security Administrator**, **Security Reader** or **Reports Reader** role for the tenant. 
 
 3. Complete the [prerequisites to access the Azure Active Directory reporting API](howto-configure-prerequisites-for-reporting-api.md). 
 
diff --git a/articles/azure-monitor/app/status-monitor-v2-overview.md b/articles/azure-monitor/app/status-monitor-v2-overview.md
@@ -8,9 +8,6 @@ ms.reviewer: abinetabate
 
 # Deploy Azure Monitor Application Insights Agent for on-premises servers
 
-> [!IMPORTANT]
-> This guidance is recommended for on-premises and non-Azure cloud deployments of Application Insights Agent. We recommend a [different deployment approach for Azure virtual machines and Azure virtual machine scale sets](./azure-vm-vmss-apps.md).
-
 Application Insights Agent (formerly named Status Monitor V2) is a PowerShell module published to the [PowerShell Gallery](https://www.powershellgallery.com/packages/Az.ApplicationMonitor).
 It replaces Status Monitor.
 Telemetry is sent to the Azure portal, where you can [monitor](./app-insights-overview.md) your app.
diff --git a/articles/cosmos-db/nosql/how-to-query-container.md b/articles/cosmos-db/nosql/how-to-query-container.md
@@ -61,7 +61,7 @@ You can manage parallel query execution by tuning the following parameters:
 
 Because of the Azure Cosmos DB's ability to parallelize cross-partition queries, query latency will generally scale well as the system adds [physical partitions](../partitioning-overview.md#physical-partitions). However, RU charge will increase significantly as the total number of physical partitions increases.
 
-When you run a cross-partition query, you are essentially doing a separate query per individual physical partition. While cross-partition queries queries will use the index, if available, they are still not nearly as efficient as in-partition queries.
+When you run a cross-partition query, you are essentially doing a separate query per individual physical partition. While cross-partition queries will use the index, if available, they are still not nearly as efficient as in-partition queries.
 
 ## Useful example
 
diff --git a/articles/cosmos-db/use-metrics.md b/articles/cosmos-db/use-metrics.md
@@ -27,7 +27,7 @@ This article walks through common use cases and how Azure Cosmos DB insights can
 
    * **Insights:** This pane provides a customized monitoring experience for Azure Cosmos DB. They use the same metrics and logs that are collected in Azure Monitor and shows an aggregated view for your account.
 
-1. Open the **Insights** pane. By default, the Insights pane shows the throughput, requests, storage, availability, latency, system, and account management metrics for ever container in your account. You can select the **Time Range**, **Database**, and **Container** for which you want to view insights. The **Overview** tab shows RU/s usage, data usage, index usage, throttled requests, and normalized RU/s consumption for the selected database and container.
+1. Open the **Insights** pane. By default, the Insights pane shows the throughput, requests, storage, availability, latency, system, and account management metrics for every container in your account. You can select the **Time Range**, **Database**, and **Container** for which you want to view insights. The **Overview** tab shows RU/s usage, data usage, index usage, throttled requests, and normalized RU/s consumption for the selected database and container.
 
    :::image type="content" source="./media/use-metrics/performance-metrics.png" alt-text="Azure Cosmos DB performance metrics in Azure portal" lightbox="./media/use-metrics/performance-metrics.png" :::
 
@@ -41,7 +41,7 @@ This article walks through common use cases and how Azure Cosmos DB insights can
 
    * **Availability** - This tab shows the percentage of successful requests over the total requests per hour. The success rate is defined by the Azure Cosmos DB SLAs.
 
-   * **Latency** - This tab shows the read and write latency observed by Azure Cosmos DB in the region where your account is operating. You can visualize latency across regions for a geo-replicated account. You can also server-side latency by different operations. This metric doesn't represent the end-to-end request latency.
+   * **Latency** - This tab shows the read and write latency observed by Azure Cosmos DB in the region where your account is operating. You can visualize latency across regions for a geo-replicated account. You can also view server-side latency by different operations. This metric doesn't represent the end-to-end request latency.
 
    * **System** - This tab shows how many metadata requests are served by the primary partition. It also helps to identify the throttled requests.
 
@@ -104,7 +104,7 @@ FeedResponse<dynamic> result = await query.ExecuteNextAsync();
 IReadOnlyDictionary<string, QueryMetrics> metrics = result.QueryMetrics;
 ```
 
-*QueryMetrics* provides details on how long each component of the query took to execution. The most common root cause for long running queries is scans, meaning the query was unable to leverage the indexes. This problem can be resolved with a better filter condition.
+*QueryMetrics* provides details on how long each component of the query took to execute. The most common root cause for long running queries is scans, meaning the query was unable to leverage the indexes. This problem can be resolved with a better filter condition.
 
 ## Next steps
 
