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/azure-functions/functions-dotnet-class-library.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,6 @@ Azure Functions supports C# and C# script programming languages. If you're looki
31
31
32
32
### Updating to target .NET 8
33
33
34
-
> [!NOTE]
35
-
> Targeting .NET 8 with the in-process model is not yet enabled for apps in sovereign clouds. Updates will be communicated on [this tracking thread on GitHub](https://github.com/Azure/azure-functions-host/issues/9951).
36
-
37
34
Apps using the in-process model can target .NET 8 by following the steps outlined in this section. However, if you choose to exercise this option, you should still begin planning your [migration to the isolated worker model](./migrate-dotnet-to-isolated-model.md) in advance of [support ending for the in-process model on November 10, 2026](https://aka.ms/azure-functions-retirements/in-process-model).
38
35
39
36
Many apps can change the configuration of the function app in Azure without updates to code or redeployment. To run .NET 8 with the in-process model, three configurations are required:
# Enable Snapshot Debugger for .NET apps in Azure App Service
14
14
15
-
Snapshot Debugger currently supports ASP.NET and ASP.NET Core apps that are running on Azure App Service on Windows service plans.
16
-
17
15
> [!NOTE]
18
-
> We recommend that you run your application on the Basic service tier, or higher, when using Snapshot Debugger. For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots. The Consumption tier is not currently available for Snapshot Debugger.
16
+
> If you're using a preview version of .NET Core, or your application references Application Insights SDK (directly or indirectly via a dependent assembly), follow the instructions for [Enable Snapshot Debugger for other environments](snapshot-debugger-vm.md) to include the [`Microsoft.ApplicationInsights.SnapshotCollector`](https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector) NuGet package with the application.
Snapshot Debugger currently supports ASP.NET and ASP.NET Core apps running on Azure App Service on Windows service plans.
21
19
22
-
Snapshot Debugger is pre-installed as part of the App Services runtime, but you need to turn it on to get snapshots for your App Service app. To enable Snapshot Debugger for an app, follow the instructions below:
20
+
We recommend that you run your application on the Basic or higher service tiers when using Snapshot Debugger. For most applications:
21
+
- The Free and Shared service tiers don't have enough memory or disk space to save snapshots.
22
+
- The Consumption tier isn't currently available for Snapshot Debugger.
23
23
24
-
> [!NOTE]
25
-
> If you're using a preview version of .NET Core, or your application references Application Insights SDK (directly or indirectly via a dependent assembly), follow the instructions for [Enable Snapshot Debugger for other environments](snapshot-debugger-vm.md) to include the [`Microsoft.ApplicationInsights.SnapshotCollector`](https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector) NuGet package with the application.
24
+
Although Snapshot Debugger is preinstalled as part of the App Services runtime, you need to turn it on to get snapshots for your App Service app. Codeless installation of Snapshot Debugger follows [the .NET Core support policy.](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
26
25
27
-
> [!NOTE]
28
-
> Codeless installation of Application Insights Snapshot Debugger follows the .NET Core support policy.
29
-
> For more information about supported runtimes, see [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
26
+
# [Azure portal](#tab/portal)
30
27
31
-
After you've deployed your .NET app:
28
+
After you've deployed your .NET App Services web app:
32
29
33
-
1.Go to the Azure control panel for your App Service.
34
-
1.Go to the **Settings** > **Application Insights** page.
30
+
1.Navigate to your App Service in the Azure portal.
31
+
1.In the left-side menu, select **Settings** > **Application Insights**.
35
32
36
33
:::image type="content" source="./media/snapshot-debugger/application-insights-app-services.png" alt-text="Screenshot showing the Enable App Insights on App Services portal.":::
37
34
38
-
1. Either follow the instructions on the page to create a new resource or select an existing App Insights resource to monitor your app.
39
-
1. Switch Snapshot Debugger toggles to **On**.
35
+
1. Click **Turn on Application Insights**.
36
+
- If you have an existing Application Insights resource you'd rather use, select that option under **Change your resource**.
37
+
1. Under **Instrument your application**, select the **.NET** tab.
38
+
1. Switch both Snapshot Debugger toggles to **On**.
40
39
41
40
:::image type="content" source="./media/snapshot-debugger/enablement-ui.png" alt-text="Screenshot showing how to add App Insights site extension.":::
42
41
43
-
1. Snapshot Debugger is now enabled using an App Services App Setting.
42
+
1. Snapshot Debugger is now enabled.
44
43
45
44
:::image type="content" source="./media/snapshot-debugger/snapshot-debugger-app-setting.png" alt-text="Screenshot showing App Setting for Snapshot Debugger.":::
46
45
47
-
If you're running a different type of Azure service, here are instructions for enabling Snapshot Debugger on other supported platforms:
*[Azure Service Fabric services](snapshot-debugger-vm.md?toc=/azure/azure-monitor/toc.json)
52
-
*[Azure Virtual Machines and Virtual Machine Scale Sets](snapshot-debugger-vm.md?toc=/azure/azure-monitor/toc.json)
53
-
*[On-premises virtual or physical machines](snapshot-debugger-vm.md?toc=/azure/azure-monitor/toc.json)
54
-
55
-
## Enable Snapshot Debugger for other clouds
56
-
57
-
Currently the only regions that require endpoint modifications are [Azure Government](../../azure-government/compare-azure-government-global-azure.md#application-insights) and [Microsoft Azure operated by 21Vianet](/azure/china/resources-developer-guide) through the Application Insights Connection String.
58
-
59
-
|Connection String Property | US Government Cloud | China Cloud |
For more information about other connection overrides, see [Application Insights documentation](../app/sdk-connection-string.md?tabs=net#connection-string-with-explicit-endpoint-overrides).
## Enable Microsoft Entra authentication for snapshot ingestion
68
-
69
-
Application Insights Snapshot Debugger supports Microsoft Entra authentication for snapshot ingestion. This means, for all snapshots of your application to be ingested, your application must be authenticated and provide the required application settings to the Snapshot Debugger agent.
70
-
71
-
As of today, Snapshot Debugger only supports Microsoft Entra authentication when you reference and configure Microsoft Entra ID using the Application Insights SDK in your application.
72
-
73
-
To turn-on Microsoft Entra ID for snapshot ingestion:
74
-
75
-
1. Create and add the managed identity you want to use to authenticate against your Application Insights resource to your App Service.
76
-
77
-
1. For System-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-system-assigned-identity).
78
-
79
-
1. For User-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-user-assigned-identity).
80
-
81
-
1. Configure and turn on Microsoft Entra ID in your Application Insights resource. For more information, see the following [documentation](../app/azure-ad-authentication.md?tabs=net#configure-and-enable-azure-ad-based-authentication)
82
-
1. Add the following application setting, used to let Snapshot Debugger agent know which managed identity to use:
@@ -139,19 +92,63 @@ For an Azure App Service, you can set app settings within the Azure Resource Man
139
92
},
140
93
```
141
94
142
-
## Not Supported Scenarios
95
+
---
96
+
97
+
Generate traffic to your application that can trigger an exception. Then, wait 10 to 15 minutes for snapshots to be sent to the Application Insights instance.
98
+
99
+
## Enable Snapshot Debugger for other cloud regions
100
+
101
+
Currently the only regions that require endpoint modifications are [Azure Government](../../azure-government/compare-azure-government-global-azure.md#application-insights) and [Microsoft Azure operated by 21Vianet](/azure/china/resources-developer-guide) through the Application Insights Connection String.
102
+
103
+
|Connection String Property | US Government Cloud | China Cloud |
For more information about other connection overrides, see [Application Insights documentation](../app/sdk-connection-string.md?tabs=net#connection-string-with-explicit-endpoint-overrides).
108
+
109
+
## Configure Snapshot Debugger
110
+
111
+
### Enable Microsoft Entra authentication for snapshot ingestion
112
+
113
+
Snapshot Debugger supports Microsoft Entra authentication for snapshot ingestion. For all snapshots of your application to be ingested, your application must be authenticated and provide the required application settings to the Snapshot Debugger agent.
114
+
115
+
As of today, Snapshot Debugger only supports Microsoft Entra authentication when you reference and configure Microsoft Entra ID using the Application Insights SDK in your application.
116
+
117
+
To turn on Microsoft Entra ID for snapshot ingestion in your App Services resource:
118
+
119
+
1. Add the managed identity that authenticates against your Application Insights resource to your App Service. You can create either:
120
+
121
+
-[Add a System-Assigned Managed identity](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-system-assigned-identity).
122
+
-[Add a User-Assigned Managed identity](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-user-assigned-identity).
123
+
124
+
1. Configure and turn on Microsoft Entra ID in your Application Insights resource. For more information, see the following [documentation](../app/azure-ad-authentication.md?tabs=net#configure-and-enable-azure-ad-based-authentication)
125
+
126
+
1. Add the following application setting. This setting tells the Snapshot Debugger agent which managed identity to use:
|APPLICATIONINSIGHTS_AUTHENTICATION_STRING | Authorization=AD;ClientID={Client ID of the User-Assigned Identity} |
139
+
140
+
## Unsupported scenarios
143
141
144
142
Below you can find scenarios where Snapshot Collector isn't supported:
145
143
146
144
|Scenario | Side Effects | Recommendation |
147
145
|------------|--------------|----------------|
148
-
|You're using the Snapshot Collector SDK in your application directly (*.csproj*) and have enabled the advanced option "Interop".| The local Application Insights SDK (including Snapshot Collector telemetry) will be lost and no Snapshots will be available. <br/> Your application could crash at startup with `System.ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.` <br/> [Learn more about the Application Insights feature "Interop".](../app/azure-web-apps-net-core.md#troubleshooting)| If you're using the advanced option "Interop", use the codeless Snapshot Collector injection (enabled through the Azure portal). |
146
+
|You're using the Snapshot Collector SDK in your application directly (*.csproj*) and enabled the advanced option "Interop".| The local Application Insights SDK (including Snapshot Collector telemetry) are lost and no Snapshots are available. <br/> Your application could crash at startup with `System.ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.` <br/> [Learn more about the Application Insights feature "Interop".](../app/azure-web-apps-net-core.md#troubleshooting)| If you're using the advanced option "Interop", use the codeless Snapshot Collector injection (enabled through the Azure portal). |
149
147
150
148
## Next steps
151
149
152
-
* Generate traffic to your application that can trigger an exception. Then, wait 10 to 15 minutes for snapshots to be sent to the Application Insights instance.
153
-
* See [snapshots](snapshot-debugger-data.md?toc=/azure/azure-monitor/toc.json#view-snapshots-in-the-portal) in the Azure portal.
154
-
* For help with troubleshooting Snapshot Debugger issues, see [Snapshot Debugger troubleshooting](snapshot-debugger-troubleshoot.md).
150
+
- View [snapshots](snapshot-debugger-data.md?toc=/azure/azure-monitor/toc.json#access-debug-snapshots-in-the-portal) in the Azure portal.
0 commit comments