Skip to content

Commit ce6eb24

Browse files
Merge pull request #79380 from MicrosoftDocs/master
Merge master to live 2:31 AM
2 parents 00d55f4 + 7a17b3d commit ce6eb24

File tree

56 files changed

+1054
-561
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+1054
-561
lines changed
Loading
Loading

articles/active-directory/privileged-identity-management/pim-how-to-use-audit-log.md

Lines changed: 33 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -11,54 +11,60 @@ ms.service: active-directory
1111
ms.topic: conceptual
1212
ms.workload: identity
1313
ms.subservice: pim
14-
ms.date: 02/14/2017
14+
ms.date: 06/10/2019
1515
ms.author: rolyon
1616
ms.custom: pim
1717

1818
ms.collection: M365-identity-device-management
1919
---
2020
# View audit history for Azure AD roles in PIM
21-
You can use the Azure Active Directory (Azure AD) Privileged Identity Management (PIM) audit history to see all the user assignments and activations within a given time period for all privileged roles. If you want to see the full audit history of activity in your tenant, including administrator, end user, and synchronization activity, you can use the [Azure Active Directory access and usage reports.](../reports-monitoring/overview-reports.md)
2221

23-
## Navigate to audit history
24-
From the [Azure portal](https://portal.azure.com) dashboard, select the **Azure AD Privileged Identity Management** app. From there, access the audit history by clicking **Manage privileged roles** > **Audit history** in the PIM dashboard.
22+
You can use the Azure Active Directory (Azure AD) Privileged Identity Management (PIM) audit history to see all the role assignments and activations within the past 30 days for all privileged roles. If you want to see the full audit history of activity in your directory, including administrator, end user, and synchronization activity, you can use the [Azure Active Directory security and activity reports](../reports-monitoring/overview-reports.md).
2523

26-
![Audit history](media/azure-ad-pim-approval-workflow/image021.png)
24+
## View audit history
2725

28-
> [!NOTE]
29-
> You can sort the data by Action, and look for “Activation Approved”
26+
Follow these steps to view the audit history for Azure AD roles.
3027

28+
1. Sign in to [Azure portal](https://portal.azure.com/) with a user that is a member of the [Privileged Role Administrator](../users-groups-roles/directory-assign-admin-roles.md#privileged-role-administrator) role.
3129

32-
## Audit history graph
33-
You can use the audit history to view the total activations, max activations per day, and average activations per day in a line graph. You can also filter the data by role if there is more than one role in the audit history.
30+
1. Open **Azure AD Privileged Identity Management**.
3431

35-
Use the **time**, **action**, and **role** buttons to sort the history.
32+
1. Click **Azure AD roles**.
3633

37-
## Audit history list
38-
The columns in the audit history list are:
34+
1. Click **Directory roles audit history**.
3935

40-
* **Requestor** - the user who requested the role activation or change. If the value is "Azure System", check the Azure audit history for more information.
41-
* **User** - the user who is activating or assigned to a role.
42-
* **Role** - the role assigned or activated by the user.
43-
* **Action** - the actions taken by the requestor. This can include assignment, unassignment, activation, or deactivation.
44-
* **Time** - when the action occurred.
45-
* **Reasoning** - if any text was entered into the reason field during activation, it will show up here.
46-
* **Expiration** - only relevant for activation of roles.
36+
Depending on your audit history, a column chart is displayed along with the total activations, max activations per day, and average activations per day.
37+
38+
![Directory roles audit history](media/pim-how-to-use-audit-log/directory-roles-audit-history.png)
39+
40+
At the bottom of the page, a table is displayed with information about each action in the available audit history. The columns have the following meanings:
41+
42+
| Column | Description |
43+
| --- | --- |
44+
| Time | When the action occurred. |
45+
| Requestor | User who requested the role activation or change. If the value is **Azure System**, check the Azure audit history for more information. |
46+
| Action | Actions taken by the requestor. Actions can include Assign, Unassign, Activate, Deactivate, or AddedOutsidePIM. |
47+
| Member | User who is activating or assigned to a role. |
48+
| Role | Role assigned or activated by the user. |
49+
| Reasoning | Text that was entered into the reason field during activation. |
50+
| Expiration | When an activated role expires. Applies only to eligible role assignments. |
51+
52+
1. To sort the audit history, click the **Time**, **Action**, and **Role** buttons.
4753

4854
## Filter audit history
49-
You can filter the information that shows up in the audit history by clicking the **Filter** button. The **Update chart parameters blade** will appear.
5055

51-
After you set the filters, click **Update** to filter the data in the history. If the data doesn't appear right away, refresh the page.
56+
1. At the top of the audit history page, click the **Filter** button.
57+
58+
The **Update chart parameters** pane appears.
59+
60+
1. In **Time range**, select a time range.
5261

53-
### Change the date range
54-
Use the **Today**, **Past Week**, **Past Month**, or **Custom** buttons to change the time range of the audit history.
62+
1. In **Roles**, add checkmarks for the roles you want to view.
5563

56-
When you choose the **Custom** button, you will be given a **From** date field and a **To** date field to specify a range of dates for the history. You can either enter the dates in MM/DD/YYYY format or click on the **calendar** icon and choose the date from a calendar.
64+
![Update chart parameters pane](media/pim-how-to-use-audit-log/update-chart-parameters.png)
5765

58-
### Change the roles included in the history
59-
Check or uncheck the **Role** checkbox next to each role to include or exclude it from the history.
66+
1. Click **Done** to view the filtered audit history.
6067

61-
<!--Every topic should have next steps and links to the next logical set of content to keep the customer engaged-->
6268
## Next steps
6369

6470
- [View activity and audit history for Azure resource roles in PIM](azure-pim-resource-rbac.md)

articles/app-service/containers/configure-language-java.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -476,9 +476,7 @@ App Service for Linux supports two runtimes for managed hosting of Java web appl
476476
477477
### JDK versions and maintenance
478478
479-
Azure's supported Java Development Kit (JDK) is [Zulu](https://www.azul.com/downloads/azure-only/zulu/) provided through [Azul Systems](https://www.azul.com/).
480-
481-
Major version updates will be provided through new runtime options in Azure App Service for Linux. Customers update to these newer versions of Java by configuring their App Service deployment and are responsible for testing and ensuring the major update meets their needs.
479+
Azul Zulu Enterprise builds of OpenJDK are a no-cost, multi-platform, production-ready distribution of the OpenJDK for Azure and Azure Stack backed by Microsoft and Azul Systems. They contain all the components for building and running Java SE applications. You can install the JDK from [Java JDK Installation](https://aka.ms/azure-jdks).
482480
483481
Supported JDKs are automatically patched on a quarterly basis in January, April, July, and October of each year.
484482
@@ -490,18 +488,6 @@ Patches and fixes for major security vulnerabilities will be released as soon as
490488
491489
If a supported Java runtime will be retired, Azure developers using the affected runtime will be given a deprecation notice at least six months before the runtime is retired.
492490
493-
### Local development
494-
495-
Developers can download the Production Edition of Azul Zulu Enterprise JDK for local development from [Azul's download site](https://www.azul.com/downloads/azure-only/zulu/).
496-
497-
### Development support
498-
499-
Product support for the [Azure-supported Azul Zulu JDK](https://www.azul.com/downloads/azure-only/zulu/) is available through when developing for Azure or [Azure Stack](https://azure.microsoft.com/overview/azure-stack/) with a [qualified Azure support plan](https://azure.microsoft.com/support/plans/).
500-
501-
### Runtime support
502-
503-
Developers can [open an issue](/azure/azure-supportability/how-to-create-azure-support-request) with the Azul Zulu JDKs through Azure Support if they have a [qualified support plan](https://azure.microsoft.com/support/plans/).
504-
505491
## Next steps
506492
507493
Visit the [Azure for Java Developers](/java/azure/) center to find Azure quickstarts, tutorials, and Java reference documentation.
Lines changed: 148 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,148 @@
1+
---
2+
title: Azure Monitor - Azure Application Insights override default SDK endpoints | Microsoft Docs
3+
description: Modify default Azure Application Insights SDK endpoints for regions like Azure Government.
4+
services: application-insights
5+
author: mrbullwinkle
6+
manager: carmonm
7+
ms.assetid: 3b722e47-38bd-4667-9ba4-65b7006c074c
8+
ms.service: application-insights
9+
ms.workload: tbd
10+
ms.tgt_pltfrm: ibiza
11+
ms.topic: conceptual
12+
ms.date: 06/10/2019
13+
ms.author: mbullwin
14+
---
15+
16+
# Application Insights overriding default endpoints
17+
18+
To send data from Application Insights to certain regions, you'll need to override the default endpoint addresses. Each SDK requires slightly different modifications, all of which are described in this article. These changes require adjusting the sample code and replacing the placeholder values for `QuickPulse_Endpoint_Address`, `TelemetryChannel_Endpoint_Address`, and `Profile_Query_Endpoint_address` with the actual endpoint addresses for your specific region. The end of this article contains links to the endpoint addresses for regions where this configuration is required.
19+
20+
## SDK code changes
21+
22+
### .NET with applicationinsights.config
23+
24+
```xml
25+
<ApplicationInsights>
26+
...
27+
<TelemetryModules>
28+
<Add Type="Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse.QuickPulseTelemetryModule, Microsoft.AI.PerfCounterCollector">
29+
<QuickPulseServiceEndpoint>Custom_QuickPulse_Endpoint_Address</QuickPulseServiceEndpoint>
30+
</Add>
31+
</TelemetryModules>
32+
...
33+
<TelemetryChannel>
34+
<EndpointAddress>TelemetryChannel_Endpoint_Address</EndpointAddress>
35+
</TelemetryChannel>
36+
...
37+
<ApplicationIdProvider Type="Microsoft.ApplicationInsights.Extensibility.Implementation.ApplicationId.ApplicationInsightsApplicationIdProvider, Microsoft.ApplicationInsights">
38+
<ProfileQueryEndpoint>Profile_Query_Endpoint_address</ProfileQueryEndpoint>
39+
</ApplicationIdProvider>
40+
...
41+
</ApplicationInsights>
42+
```
43+
44+
### .NET Core
45+
46+
Modify the appsettings.json file in your project as follows to adjust the main endpoint:
47+
48+
```json
49+
"ApplicationInsights": {
50+
"InstrumentationKey": "instrumentationkey",
51+
"TelemetryChannel": {
52+
"EndpointAddress": "TelemetryChannel_Endpoint_Address"
53+
}
54+
}
55+
```
56+
57+
The values for Live Metrics and the Profile Query Endpoint can only be set via code. To override the default values for all endpoint values via code, make the following changes in the `ConfigureServices` method of the `Startup.cs` file:
58+
59+
```csharp
60+
using Microsoft.ApplicationInsights.Extensibility.Implementation.ApplicationId;
61+
using Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse; //place at top of Startup.cs file
62+
63+
services.ConfigureTelemetryModule<QuickPulseTelemetryModule>((module, o) => module.QuickPulseServiceEndpoint="QuickPulse_Endpoint_Address");
64+
65+
services.AddSingleton(new ApplicationInsightsApplicationIdProvider() { ProfileQueryEndpoint = "Profile_Query_Endpoint_address" });
66+
67+
services.AddSingleton<ITelemetryChannel>(new ServerTelemetryChannel() { EndpointAddress = "TelemetryChannel_Endpoint_Address" });
68+
69+
//place in ConfigureServices method. If present, place this prior to services.AddApplicationInsightsTelemetry("instrumentation key");
70+
```
71+
72+
### Java
73+
74+
Modify the applicationinsights.xml file to change the default endpoint address.
75+
76+
```xml
77+
<?xml version="1.0" encoding="utf-8"?>
78+
<ApplicationInsights xmlns="http://schemas.microsoft.com/ApplicationInsights/2013/Settings">
79+
<InstrumentationKey>ffffeeee-dddd-cccc-bbbb-aaaa99998888</InstrumentationKey>
80+
<TelemetryModules>
81+
<Add type="com.microsoft.applicationinsights.web.extensibility.modules.WebRequestTrackingTelemetryModule"/>
82+
<Add type="com.microsoft.applicationinsights.web.extensibility.modules.WebSessionTrackingTelemetryModule"/>
83+
<Add type="com.microsoft.applicationinsights.web.extensibility.modules.WebUserTrackingTelemetryModule"/>
84+
</TelemetryModules>
85+
<TelemetryInitializers>
86+
<Add type="com.microsoft.applicationinsights.web.extensibility.initializers.WebOperationIdTelemetryInitializer"/>
87+
<Add type="com.microsoft.applicationinsights.web.extensibility.initializers.WebOperationNameTelemetryInitializer"/>
88+
<Add type="com.microsoft.applicationinsights.web.extensibility.initializers.WebSessionTelemetryInitializer"/>
89+
<Add type="com.microsoft.applicationinsights.web.extensibility.initializers.WebUserTelemetryInitializer"/>
90+
<Add type="com.microsoft.applicationinsights.web.extensibility.initializers.WebUserAgentTelemetryInitializer"/>
91+
</TelemetryInitializers>
92+
<!--Add the following Channel value to modify the Endpoint address-->
93+
<Channel type="com.microsoft.applicationinsights.channel.concrete.inprocess.InProcessTelemetryChannel">
94+
<EndpointAddress>TelemetryChannel_Endpoint_Address</EndpointAddress>
95+
</Channel>
96+
</ApplicationInsights>
97+
```
98+
99+
### Spring Boot
100+
101+
Modify the `application.properties` file and add:
102+
103+
```yaml
104+
azure.application-insights.channel.in-process.endpoint-address= TelemetryChannel_Endpoint_Address
105+
```
106+
107+
### Node.js
108+
109+
```javascript
110+
var appInsights = require("applicationinsights");
111+
appInsights.setup('INSTRUMENTATION_KEY');
112+
appInsights.defaultClient.config.endpointUrl = "TelemetryChannel_Endpoint_Address"; // ingestion
113+
appInsights.defaultClient.config.profileQueryEndpoint = "Profile_Query_Endpoint_address"; // appid/profile lookup
114+
appInsights.defaultClient.config.quickPulseHost = "QuickPulse_Endpoint_Address"; //live metrics
115+
appInsights.Configuration.start();
116+
```
117+
118+
The endpoints can also be configured through environment variables:
119+
120+
```
121+
Instrumentation Key: “APPINSIGHTS_INSTRUMENTATIONKEY”
122+
Profile Endpoint: “Profile_Query_Endpoint_address”
123+
Live Metrics Endpoint: "QuickPulse_Endpoint_Address"
124+
```
125+
126+
### JavaScript
127+
128+
```javascript
129+
<script type="text/javascript">
130+
var sdkInstance="appInsightsSDK";window[sdkInstance]="appInsights";var aiName=window[sdkInstance],aisdk=window[aiName]||function(e){function n(e){i[e]=function(){var n=arguments;i.queue.push(function(){i[e].apply(i,n)})}}var i={config:e};i.initialize=!0;var a=document,t=window;setTimeout(function(){var n=a.createElement("script");n.src=e.url||"https://az416426.vo.msecnd.net/next/ai.2.min.js",a.getElementsByTagName("script")[0].parentNode.appendChild(n)});try{i.cookie=a.cookie}catch(e){}i.queue=[],i.version=2;for(var r=["Event","PageView","Exception","Trace","DependencyData","Metric","PageViewPerformance"];r.length;)n("track"+r.pop());n("startTrackPage"),n("stopTrackPage");var o="Track"+r[0];if(n("start"+o),n("stop"+o),!(!0===e.disableExceptionTracking||e.extensionConfig&&e.extensionConfig.ApplicationInsightsAnalytics&&!0===e.extensionConfig.ApplicationInsightsAnalytics.disableExceptionTracking)){n("_"+(r="onerror"));var s=t[r];t[r]=function(e,n,a,t,o){var c=s&&s(e,n,a,t,o);return!0!==c&&i["_"+r]({message:e,url:n,lineNumber:a,columnNumber:t,error:o}),c},e.autoExceptionInstrumented=!0}return i}
131+
(
132+
{
133+
instrumentationKey:"INSTRUMENTATION_KEY",
134+
endpointUrl: "TelemetryChannel_Endpoint_Address"
135+
}
136+
);
137+
window[aiName]=aisdk,aisdk.queue&&0===aisdk.queue.length&&aisdk.trackPageView({});
138+
</script>
139+
140+
```
141+
142+
## Regions that require endpoint modification
143+
144+
Currently the only region that requires endpoint modifications is [Azure Government](https://docs.microsoft.com/azure/azure-government/documentation-government-services-monitoringandmanagement#application-insights).
145+
146+
## Next step
147+
148+
- To learn more about the custom modifications for Azure Government, consult the detailed guidance for [Azure monitoring and management](https://docs.microsoft.com/azure/azure-government/documentation-government-services-monitoringandmanagement#application-insights).

articles/azure-monitor/app/ip-addresses.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: application-insights
1010
ms.workload: tbd
1111
ms.tgt_pltfrm: ibiza
1212
ms.topic: conceptual
13-
ms.date: 05/21/2019
13+
ms.date: 05/31/2019
1414
ms.author: mbullwin
1515
---
1616
# IP addresses used by Application Insights and Log Analytics

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -992,6 +992,8 @@
992992
href: app/nuget.md
993993
- name: Platform support
994994
href: app/platforms.md
995+
- name: Endpoint overrides
996+
href: app/custom-endpoints.md
995997
- name: Application Insights data model
996998
items:
997999
- name: Overview

articles/cognitive-services/Anomaly-Detector/tutorials/anomaly-detection-streaming-databricks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -668,7 +668,7 @@ Result as below:
668668
+--------------------+-------+
669669
|2019-04-16T00:00:00Z| false|
670670
+--------------------+-------+
671-
671+
```
672672

673673
That's it! Using Azure Databricks, you have successfully streamed data into Azure Event Hubs, consumed the stream data using the Event Hubs connector, and then run anomaly detection on streaming data in near real time.
674674
Although in this tutorial, the granularity is hourly, you can always change the granularity to meet your need.

articles/cognitive-services/Speech-Service/how-to-use-codec-compressed-audio-input-streams.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ The Speech SDK's **Compressed Audio Input Stream** API provides a way to stream
1818

1919
> [!IMPORTANT]
2020
> Streaming compressed audio is only supported for C++, C#, and Java on Linux (Ubuntu 16.04, Ubuntu 18.04, Debian 9).
21+
> Speech SDK version 1.4.0 or higher is required.
2122
2223
For wav/PCM see the mainline speech documentation. Outside of wav/PCM, the following codec compressed input formats are supported:
2324

0 commit comments

Comments
 (0)