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-monitor/app/snapshot-debugger-upgrade.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,13 @@ ms.reviewer: mbullwin
13
13
14
14
# Upgrading the Snapshot Debugger
15
15
16
-
To provide the best possible security for your data, Microsoft is moving away from TLS 1.0 and TLS 1.1, which have been shown to be vulnerable to determined attackers. If you are using an older version of the site extension, it will require an upgrade to continue working. This document outlines the steps needed to upgrade your Snapshot debugger to the latest version.
16
+
To provide the best possible security for your data, Microsoft is moving away from TLS 1.0 and TLS 1.1, which have been shown to be vulnerable to determined attackers. If you're using an older version of the site extension, it will require an upgrade to continue working. This document outlines the steps needed to upgrade your Snapshot debugger to the latest version.
17
17
There are two primary upgrade paths depending on if you enabled the Snapshot Debugger using a site extension or if you used an SDK/Nuget added to your application. Both upgrade paths are discussed below.
18
18
19
19
## Upgrading the site extension
20
20
21
21
> [!IMPORTANT]
22
-
> Older versions of Application Insights used a private site extension called "Application Insights extension for Azure App Service". The current Application Insights experience is enabled by setting App Settings to light up a pre-installed site extension.
22
+
> Older versions of Application Insights used a private site extension called _Application Insights extension for Azure App Service_. The current Application Insights experience is enabled by setting App Settings to light up a pre-installed site extension.
23
23
> To avoid conflicts, which may cause your site to stop working, it is important to delete the private site extension first. See step 4 below.
24
24
25
25
If you enabled the Snapshot debugger using the site extension, you can upgrade using the following procedure:
@@ -29,27 +29,27 @@ If you enabled the Snapshot debugger using the site extension, you can upgrade u
29
29
30
30

31
31
32
-
3. Once you have navigated to your resource, click on the Extensions blade and wait for the list of extensions to populate:
32
+
3. Once you've navigated to your resource, click on the Extensions blade and wait for the list of extensions to populate:
33
33
34
34

35
35
36
-
4. If any version of "Application Insights extension for Azure App Service" is installed, then select it and click Delete. Confirm "Yes" to delete the extension and wait for the delete to complete before moving to the next step.
36
+
4. If any version of _Application Insights extension for Azure App Service_ is installed, then select it and click Delete. Confirm **Yes** to delete the extension and wait for the delete to complete before moving to the next step.
37
37
38
38

39
39
40
40
5. Go to the Overview blade of your resource and click on Application Insights:
41
41
42
42

43
43
44
-
6. If this is the first time you have viewed the Application Insights blade for this App Service you will be prompted to turn on Application Insights. Select "Turn on Application Insights".
44
+
6. If this is the first time you've viewed the Application Insights blade for this App Service, you'll be prompted to turn on Application Insights. Select **Turn on Application Insights**.
45
45
46
-

46
+

47
47
48
-
7. The current Application Insights settings are displayed. Unless you want to take the opportunity to change your settings, you can leave them as is. The **Apply** button on the bottom of the blade is not enabled by default and you will have to toggle one of the settings to activate the button. You don’t have to change any actual settings, rather you can change the setting and then immediately change it back. We recommend toggling the Profiler setting and then selecting **Apply**.
48
+
7. The current Application Insights settings are displayed. Unless you want to take the opportunity to change your settings, you can leave them as is. The **Apply** button on the bottom of the blade isn't enabled by default and you'll have to toggle one of the settings to activate the button. You don’t have to change any actual settings, rather you can change the setting and then immediately change it back. We recommend toggling the Profiler setting and then selecting **Apply**.
49
49
50
50

51
51
52
-
8. Once you click **Apply**, you will be asked to confirm the changes.
52
+
8. Once you click **Apply**, you'll be asked to confirm the changes.
53
53
54
54
> [!NOTE]
55
55
> The site will be restarted as part of the upgrade process.
0 commit comments