Skip to content

Commit e80eab9

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-horizontal-rbac-terms
2 parents 6fae8b9 + 5e91fc8 commit e80eab9

24 files changed

+46
-31
lines changed

articles/active-directory/conditional-access/concept-conditional-access-report-only.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 03/25/2020
9+
ms.date: 05/01/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -23,7 +23,7 @@ Report-only mode is a new Conditional Access policy state that allows administra
2323

2424
- Conditional Access policies can be enabled in report-only mode.
2525
- During sign-in, policies in report-only mode are evaluated but not enforced.
26-
- Results are logged in the **Conditional Access** and **Report-only (Preview)** tabs of the Sign-in log details.
26+
- Results are logged in the **Conditional Access** and **Report-only** tabs of the Sign-in log details.
2727
- Customers with an Azure Monitor subscription can monitor the impact of their Conditional Access policies using the Conditional Access insights workbook.
2828

2929
> [!WARNING]

articles/active-directory/conditional-access/howto-conditional-access-insights-reporting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: article
9-
ms.date: 04/30/2020
9+
ms.date: 05/01/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo

articles/active-directory/conditional-access/howto-conditional-access-report-only.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 03/25/2020
9+
ms.date: 05/01/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -15,7 +15,7 @@ ms.reviewer: dawoo
1515

1616
ms.collection: M365-identity-device-management
1717
---
18-
# Configure a Conditional Access policy in report-only mode (Preview)
18+
# Configure a Conditional Access policy in report-only mode
1919

2020
To configure a Conditional Access policy in report-only mode:
2121

@@ -39,7 +39,7 @@ To view the result of a report-only policy for a particular sign-in:
3939
1. Sign into the **Azure portal** as a reports reader, security reader, security administrator, or global administrator.
4040
1. Browse to **Azure Active Directory** > **Sign-ins**.
4141
1. Select a sign-in or add filters to narrow results.
42-
1. In the **Details** drawer, select the **Report-only (Preview)** tab to view the policies evaluated during sign-in.
42+
1. In the **Details** drawer, select the **Report-only** tab to view the policies evaluated during sign-in.
4343

4444
> [!NOTE]
4545
> When downloading the Sign-ins logs, choose JSON format to include Conditional Access report-only result data.
@@ -59,7 +59,7 @@ Once you've integrated your Azure AD logs with Azure Monitor, you can monitor th
5959

6060
1. Sign into the **Azure portal** as a security administrator or global administrator.
6161
1. Browse to **Azure Active Directory** > **Workbooks**.
62-
1. Select **Conditional Access Insights (Preview)**.
62+
1. Select **Conditional Access Insights**.
6363
1. Select one or more policies from the **Conditional Access Policy** dropdown. All enabled policies are selected by default.
6464
1. Select a time range (if the time range exceeds the available dataset, the report will show all available data). Once you have set the **Conditional Access Policy** and **Time Range** parameters, the report will load.
6565
1. Optionally, search for individual **Users** or **Apps** to narrow the scope of the report.
Loading
Loading
Loading
Loading

articles/active-directory/reports-monitoring/howto-use-azure-monitor-workbooks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ including device platform, device state, client app, sign-in risk, location, and
4343
reports how many users were granted or denied access, as well as how many users bypassed
4444
Conditional Access policies when accessing resources.
4545

46-
- To help you to address these questions, Active Directory provides workbooks for monitoring. [Azure Monitor workbooks](https://docs.microsoft.com/azure/azure-monitor/app/usage-workbooks) combine text, analytics queries, metrics, and parameters into rich interactive reports.
46+
- To help you to address these questions, Azure Active Directory provides workbooks for monitoring. [Azure Monitor workbooks](https://docs.microsoft.com/azure/azure-monitor/app/usage-workbooks) combine text, analytics queries, metrics, and parameters into rich interactive reports.
4747

4848

4949

@@ -59,7 +59,7 @@ This article:
5959

6060
To use Monitor workbooks, you need:
6161

62-
- An Active Directory tenant with a premium (P1 or P2) license. Learn how to [get a premium license](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-get-started-premium).
62+
- An Azure Active Directory tenant with a premium (P1 or P2) license. Learn how to [get a premium license](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-get-started-premium).
6363

6464
- A [Log Analytics workspace](https://docs.microsoft.com/azure/azure-monitor/learn/quick-create-workspace).
6565

articles/azure-monitor/app/custom-operations-tracking.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Let's see how such operations could be tracked.
3434
On a high level, the task is to create `RequestTelemetry` and set known properties. After the operation is finished, you track the telemetry. The following example demonstrates this task.
3535

3636
### HTTP request in Owin self-hosted app
37-
In this example, trace context is propagated according to the [HTTP Protocol for Correlation](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/HttpCorrelationProtocol.md). You should expect to receive headers that are described there.
37+
In this example, trace context is propagated according to the [HTTP Protocol for Correlation](https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/HttpCorrelationProtocol.md). You should expect to receive headers that are described there.
3838

3939
```csharp
4040
public class ApplicationInsightsMiddleware : OwinMiddleware
@@ -113,7 +113,7 @@ public class ApplicationInsightsMiddleware : OwinMiddleware
113113
The HTTP Protocol for Correlation also declares the `Correlation-Context` header. However, it's omitted here for simplicity.
114114

115115
## Queue instrumentation
116-
While there are [W3C Trace Context](https://www.w3.org/TR/trace-context/) and [HTTP Protocol for Correlation](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/HttpCorrelationProtocol.md) to pass correlation details with HTTP request, every queue protocol has to define how the same details are passed along the queue message. Some queue protocols (such as AMQP) allow passing additional metadata and some others (such Azure Storage Queue) require the context to be encoded into the message payload.
116+
While there are [W3C Trace Context](https://www.w3.org/TR/trace-context/) and [HTTP Protocol for Correlation](https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/HttpCorrelationProtocol.md) to pass correlation details with HTTP request, every queue protocol has to define how the same details are passed along the queue message. Some queue protocols (such as AMQP) allow passing additional metadata and some others (such Azure Storage Queue) require the context to be encoded into the message payload.
117117

118118
> [!NOTE]
119119
> * **Cross-component tracing is not supported for queues yet** With HTTP, if your producer and consumer send telemetry to different Application Insights resources, Transaction Diagnostics Experience and Application Map show transactions and map end-to-end. In case of queues this is not supported yet.
@@ -343,7 +343,7 @@ When you instrument message deletion, make sure you set the operation (correlati
343343

344344
### Dependency Types
345345

346-
Application Insights uses dependency type to cusomize UI experiences. For queues it recognizes following types of `DependencyTelemetry` that improve [Transaction diagnostics experience](/azure/azure-monitor/app/transaction-diagnostics):
346+
Application Insights uses dependency type to customize UI experiences. For queues it recognizes following types of `DependencyTelemetry` that improve [Transaction diagnostics experience](/azure/azure-monitor/app/transaction-diagnostics):
347347
- `Azure queue` for Azure Storage Queues
348348
- `Azure Event Hubs` for Azure Event Hubs
349349
- `Azure Service Bus` for Azure Service Bus
@@ -479,4 +479,4 @@ Each Application Insights operation (request or dependency) involves `Activity`
479479
- See the [data model](../../azure-monitor/app/data-model.md) for Application Insights types and data model.
480480
- Report custom [events and metrics](../../azure-monitor/app/api-custom-events-metrics.md) to Application Insights.
481481
- Check out standard [configuration](configuration-with-applicationinsights-config.md#telemetry-initializers-aspnet) for context properties collection.
482-
- Check the [System.Diagnostics.Activity User Guide](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/ActivityUserGuide.md) to see how we correlate telemetry.
482+
- Check the [System.Diagnostics.Activity User Guide](https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/ActivityUserGuide.md) to see how we correlate telemetry.

articles/cognitive-services/Computer-vision/QuickStarts/python-analyze.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: nitinme
99
ms.service: cognitive-services
1010
ms.subservice: computer-vision
1111
ms.topic: quickstart
12-
ms.date: 04/14/2020
12+
ms.date: 05/01/2020
1313
ms.author: pafarley
1414
ms.custom: seodec18
1515
---

0 commit comments

Comments
 (0)