You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/concept-certificate-based-authentication-smartcard.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,11 @@ The Windows smart card sign-in works with the latest preview build of Windows 11
73
73
|✅|✅|✅|✅|
74
74
75
75
>[!NOTE]
76
-
>Azure AD CBA supports both certificates on-device as well as external storage like security keys on Windows.
76
+
>Azure AD CBA supports both certificates on-device as well as external storage like security keys on Windows.
77
+
78
+
## Windows Out of the box experience (OOBE)
79
+
80
+
Windows OOBE should allow the user to login using an external smart card reader and authenticate against Azure AD CBA. Windows OOBE by default should have the necessary smart card drivers or the smart card drivers previously added to the Windows image before OOBE setup.
Copy file name to clipboardExpand all lines: articles/active-directory/reports-monitoring/concept-provisioning-logs.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -241,6 +241,7 @@ Use the following table to better understand how to resolve errors that you find
241
241
> | AzureActiveDirectoryCannotUpdateObjectsOriginatedInExternalService | The synchronization engine could not update one or more user properties in the target tenant.<br/><br/>The operation failed in Microsoft Graph API because of Source of Authority (SOA) enforcement. Currently, the following properties show up in the list:<br/>`Mail`<br/>`showInAddressList`| In some cases (for example when `showInAddressList` property is part of the user update), the synchronization engine might automatically retry the (user) update without the offending property. Otherwise, you will need to update the property directly in the target tenant. |
242
242
> | AzureDirectoryB2BManagementPolicyCheckFailure | The cross-tenant synchronization policy allowing automatic redemption failed.<br/><br/>The synchronization engine checks to ensure that the administrator of the target tenant has created an inbound cross-tenant synchronization policy allowing automatic redemption. The synchronization engine also checks if the administrator of the source tenant has enabled an outbound policy for automatic redemption. | Ensure that the automatic redemption setting has been enabled for both the source and target tenants. For more information, see [Automatic redemption setting](../multi-tenant-organizations/cross-tenant-synchronization-overview.md#automatic-redemption-setting). |
243
243
> | AzureActiveDirectoryQuotaLimitExceeded | The number of objects in the tenant exceeds the directory limit.<br/><br/>Azure AD has limits for the number of objects that can be created in a tenant. | Check whether the quota can be increased. For information about the directory limits and steps to increase the quota, see [Azure AD service limits and restrictions](../enterprise-users/directory-service-limits-restrictions.md). |
244
+
> |InvitationCreationFailure| The Azure AD provisioning service attempted to invite the user in the target tenant. That invitation failed.| Navigate to the user settings page in Azure AD > external users > collaboration restrictions and ensure that collaboration with that tenant is enabled.|
You can set the `--desired-version` parameter of the `spec.update.desiredVersion` property of an Azure Arc-enabled SQL Managed Instance to `auto` to ensure that your managed instance will be upgraded after a data controller upgrade, with no interaction from a user. This setting simplifies management, as you don't need to manually upgrade every instance for every release.
Copy file name to clipboardExpand all lines: articles/azure-arc/resource-bridge/network-requirements.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,10 +42,12 @@ In addition, resource bridge (preview) requires connectivity to the [Arc-enabled
42
42
43
43
## SSL proxy configuration
44
44
45
-
Azure Arc resource bridge must be configured for proxy so that it can connect to the Azure services. This configuration is handled automatically. However, proxy configuration of the management machine isn't configured by the Azure Arc resource bridge.
45
+
If using a proxy, Azure Arc resource bridge must be configured for proxy so that it can connect to the Azure services. To configure the Arc resource bridge with proxy, provide the proxy certificate file path during creation of the configuration files. Only pass the single proxy certificate. If a certificate bundle is passed then the deployment will fail. Proxy configuration of the management machine isn't configured by the Azure Arc resource bridge.
46
46
47
47
There are only two certificates that should be relevant when deploying the Arc resource bridge behind an SSL proxy: the SSL certificate for your SSL proxy (so that the host and guest trust your proxy FQDN and can establish an SSL connection to it), and the SSL certificate of the Microsoft download servers. This certificate must be trusted by your proxy server itself, as the proxy is the one establishing the final connection and needs to trust the endpoint. Non-Windows machines may not trust this second certificate by default, so you may need to ensure that it's trusted.
48
48
49
+
50
+
49
51
## Exclusion list for no proxy
50
52
51
53
The following table contains the list of addresses that must be excluded by using the `-noProxy` parameter in the `createconfig` command.
title: Monitor applications running on Azure Functions with Application Insights - Azure Monitor | Microsoft Docs
3
-
description: Azure Monitor seamlessly integrates with your application running on Azure Functions, and allows you to monitor the performance and spot the problems with your apps in no time.
3
+
description: Azure Monitor integrates with your Azure Functions application, allowing performance monitoring and quickly identifying problems.
4
4
ms.topic: conceptual
5
-
ms.date: 11/14/2022
5
+
ms.date: 02/09/2023
6
6
ms.reviewer: abinetabate
7
7
---
8
8
9
9
# Monitoring Azure Functions with Azure Monitor Application Insights
10
10
11
-
[Azure Functions](../../azure-functions/functions-overview.md) offers built-in integration with Azure Application Insights to monitor functions. For languages other than .NET and .NETCore additional language-specific workers/extensions are needed to get the full benefits of distributed tracing.
11
+
[Azure Functions](../../azure-functions/functions-overview.md) offers built-in integration with Azure Application Insights to monitor functions. For languages other than .NET and .NET Core, other language-specific workers/extensions are needed to get the full benefits of distributed tracing.
12
12
13
13
Application Insights collects log, performance, and error data, and automatically detects performance anomalies. Application Insights includes powerful analytics tools to help you diagnose issues and to understand how your functions are used. When you have the visibility into your application data, you can continuously improve performance and usability. You can even use Application Insights during local function app project development.
14
14
15
-
The required Application Insights instrumentation is built into Azure Functions. The only thing you need is a valid instrumentation key to connect your function app to an Application Insights resource. The instrumentation key should be added to your application settings when your function app resource is created in Azure. If your function app doesn't already have this key, you can set it manually. For more information read more about [monitoring Azure Functions](../../azure-functions/functions-monitoring.md?tabs=cmd).
16
-
17
-
For a complete list of supported auto-instrumentation scenarios, see [Supported environments, languages, and resource providers](codeless-overview.md#supported-environments-languages-and-resource-providers).
15
+
The required Application Insights instrumentation is built into Azure Functions. The only thing you need is a valid connection string to connect your function app to an Application Insights resource. The connection string should be added to your application settings when your function app resource is created in Azure. If your function app doesn't already have a connection string, you can set it manually. For more information, read more about [monitoring Azure Functions](../../azure-functions/functions-monitoring.md?tabs=cmd) and [connection strings](sdk-connection-string.md).
For a complete list of supported auto-instrumentation scenarios, see [Supported environments, languages, and resource providers](codeless-overview.md#supported-environments-languages-and-resource-providers).
20
+
21
21
## Distributed tracing for Java applications (public preview)
22
22
23
23
> [!IMPORTANT]
24
24
> This feature is currently in public preview for Java Azure Functions both Windows and Linux
25
25
26
-
If your applications are written in Java you can view richer data from your functions applications, including requests, dependencies, logs, and metrics. The additional data also lets you see and diagnose end-to-end transactions and see the application map, which aggregates many transactions to show a topological view of how the systems interact, and what the average performance and error rates are.
26
+
> [!Note]
27
+
> This feature used to have a 8-9 second cold startup implication, which has been reduced to less than 1 sec. If you were an early adopter of this feature (i.e. prior to Feb 2023), then review the troubleshooting section to update to the current version and benefit from the new faster startup.
27
28
28
-
The end-to-end diagnostics and the application map provide visibility into one single transaction/request. Together these two features are helpful for finding the root cause of reliability issues and performance bottlenecks on a per request basis.
29
+
To view more data from your Java-based Azure Functions applications than is [collected by default](../../azure-functions/functions-monitoring.md?tabs=cmd), you can enable the [Application Insights Java 3.x agent](./java-in-process-agent.md). This agent allows Application Insights to automatically collect and correlate dependencies, logs, and metrics from popular libraries and Azure SDKs, in addition to the request telemetry already captured by Functions.
30
+
31
+
By using the application map and having a more complete view of end-to-end transactions, you can better diagnose issues and see a topological view of how systems interact, along with data on average performance and error rates. You have more data for end-to-end diagnostics and the ability to use the application map to easily find the root cause of reliability issues and performance bottlenecks on a per request basis.
32
+
33
+
For more advanced use cases, you're able to modify telemetry (add spans, update span status, add span attributes) or send custom telemetry using standard APIs.
29
34
30
35
### How to enable distributed tracing for Java Function apps
31
36
32
-
Navigate to the functions app Overview pane and go to configurations. Under Application Settings, click "+ New application setting".
37
+
Navigate to the functions app Overview pane and go to configurations. Under Application Settings, select "+ New application setting".
33
38
34
39
> [!div class="mx-imgBorder"]
35
40
> 
36
41
37
-
Add the following application settings with below values, then click Save on the upper left. DONE!
42
+
Add the following application settings with below values, then select Save on the upper left. DONE!
43
+
44
+
```
45
+
APPLICATIONINSIGHTS_ENABLE_AGENT: true
46
+
```
47
+
48
+
### Troubleshooting
49
+
50
+
Your Java Functions may have slow startup times if you adopted this feature before Feb 2023. Follow the steps to fix the issue.
38
51
39
52
#### Windows
53
+
54
+
1. Check to see if the following settings exist and remove them.
55
+
40
56
```
41
57
XDT_MicrosoftApplicationInsights_Java -> 1
42
58
ApplicationInsightsAgent_EXTENSION_VERSION -> ~2
43
59
```
44
-
> [!IMPORTANT]
45
-
> This feature will have a cold start implication of 8-9 seconds in the Windows Consumption plan.
60
+
61
+
2. Enable the latest version by adding this setting.
62
+
63
+
```
64
+
APPLICATIONINSIGHTS_ENABLE_AGENT: true
65
+
```
46
66
47
67
#### Linux Dedicated/Premium
68
+
69
+
1. Check to see if the following settings exist and remove it.
70
+
48
71
```
49
72
ApplicationInsightsAgent_EXTENSION_VERSION -> ~3
50
73
```
51
74
52
-
#### Linux Consumption
75
+
2. Enable the latest version by adding this setting.
76
+
53
77
```
54
78
APPLICATIONINSIGHTS_ENABLE_AGENT: true
55
79
```
56
80
57
-
### Troubleshooting
58
-
59
-
* Sometimes the latest version of the Application Insights Java agent is not
60
-
available in Azure Function - it takes a few months for the latest versions to
61
-
roll out to all regions. In case you need the latest version of Java agent to
62
-
monitor your app in Azure Function to use a specific version of Application
63
-
Insights Java Auto-instrumentation Agent, you can upload the agent manually:
64
-
65
-
Please follow this [instruction](https://github.com/Azure/azure-functions-java-worker/wiki/Distributed-Tracing-for-Java-Azure-Functions#customize-distribute-agent).
81
+
> [!NOTE]
82
+
> If the latest version of the Application Insights Java agent isn't available in Azure Function, you can upload it manually by following [these instructions](https://github.com/Azure/azure-functions-java-worker/wiki/Distributed-Tracing-for-Java-Azure-Functions#customize-distribute-agent).
0 commit comments