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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ You've decided to contribute. That's great! To contribute to the documentation,
12
12
13
13
#### GitHub
14
14
15
-
Contributing to the documentation requires a GitHub account. If you don't have an account, follow the instructions for [GitHub account setup](https://learn.microsoft.com/contribute/get-started-setup-github) from our contributor guide.
15
+
Contributing to the documentation requires a [GitHub account](https://github.com/). If you don't have an account, follow the instructions for [GitHub account setup](https://learn.microsoft.com/contribute/get-started-setup-github) from our contributor guide.
Copy file name to clipboardExpand all lines: articles/app-service/configure-authentication-file-based.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ With [App Service authentication](overview-authentication-authorization.md), the
17
17
18
18
## Enabling file-based configuration
19
19
20
-
1. Create a new JSON file for your configuration at the root of your project (deployed to D:\home\site\wwwroot in your web / function app). Fill in your desired configuration according to the [file-based configuration reference](#configuration-file-reference). If modifying an existing Azure Resource Manager configuration, make sure to translate the properties captured in the `authsettings` collection into your configuration file.
20
+
1. Create a new JSON file for your configuration at the root of your project (deployed to C:\home\site\wwwroot in your web / function app). Fill in your desired configuration according to the [file-based configuration reference](#configuration-file-reference). If modifying an existing Azure Resource Manager configuration, make sure to translate the properties captured in the `authsettings` collection into your configuration file.
21
21
22
22
2. Modify the existing configuration, which is captured in the [Azure Resource Manager](../azure-resource-manager/management/overview.md) APIs under `Microsoft.Web/sites/<siteName>/config/authsettingsV2`. To modify it, you can use an [Azure Resource Manager template](../azure-resource-manager/templates/overview.md) or a tool like [Azure Resource Explorer](https://resources.azure.com/). Within the authsettingsV2 collection, set two properties (you may remove others):
Copy file name to clipboardExpand all lines: articles/app-service/deploy-local-git.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ When you push commits to your App Service repository, App Service deploys the fi
147
147
git push azure main
148
148
```
149
149
150
-
You can also change the `DEPLOYMENT_BRANCH` app setting in the Azure portal, by selecting **Configuration** under **Settings** and adding a new Application Setting with a name of `DEPLOYMENT_BRANCH` and value of `main`.
150
+
You can also change the `DEPLOYMENT_BRANCH` app setting in the Azure portal, by selecting **Environment variables** under **Settings** and adding a new App setting with a name of `DEPLOYMENT_BRANCH` and value of `main`.
Copy file name to clipboardExpand all lines: articles/app-service/deploy-run-package.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,10 @@ The command also restarts the app. Because `WEBSITE_RUN_FROM_PACKAGE` is set, Ap
54
54
55
55
## Run from external URL instead
56
56
57
-
You can also run a package from an external URL, such as Azure Blob Storage. You can use the [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) to upload package files to your Blob storage account. You should use a private storage container with a [Shared Access Signature (SAS)](../vs-azure-tools-storage-manage-with-storage-explorer.md#generate-a-sas-in-storage-explorer) or [use a managed identity](#access-a-package-in-azure-blob-storage-using-a-managed-identity) to enable the App Service runtime to access the package securely.
57
+
You can also run a package from an external URL, such as Azure Blob Storage. You can use the [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) to upload package files to your Blob storage account. You should use a private storage container with a [Shared Access Signature (SAS)](../vs-azure-tools-storage-manage-with-storage-explorer.md#generate-a-sas-in-storage-explorer) or [use a managed identity](#access-a-package-in-azure-blob-storage-using-a-managed-identity) to enable the App Service runtime to access the package securely.
58
+
59
+
> [!NOTE]
60
+
> Currently, an existing App Service resource that runs a local package cannot be migrated to run from a remote package. You will have to create a new App Service resource configured to run from an external URL.
58
61
59
62
Once you upload your file to Blob storage and have an SAS URL for the file, set the `WEBSITE_RUN_FROM_PACKAGE` app setting to the URL. The following example does it by using Azure CLI:
Copy file name to clipboardExpand all lines: articles/app-service/includes/quickstart-custom-container/quickstart-custom-container-linux-visual-studio-code-pivot.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ In this Dockerfile, the parent image is one of the built-in Java containers of A
119
119
120
120
2.[Open the Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette), and type **Docker Images: Build Image**. Type **Enter** to run the command.
121
121
122
-
3. In the image tag box, specify the tag you want in the following format: `<acr-name>.azurecr.io/<image-name>/<tag>`, where `<acr-name>` is the name of the container registry you created. Press **Enter**.
122
+
3. In the image tag box, specify the tag you want in the following format: `<acr-name>.azurecr.io/<image-name>:<tag>`, where `<acr-name>` is the name of the container registry you created. Press **Enter**.
123
123
124
124
4. When the image finishes building, click **Refresh** at the top of the **IMAGES** explorer and verify that the image is built successfully.
|Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.8.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.8.0 ([Download](https://aka.ms/ads-azcli-ext))|
38
-
|SQL Database version | 970 |
40
+
|SQL Database version |972|
39
41
40
-
Release Notes:
41
-
- Arc SQL Server | Automatically start billing for ESU on servers that are enabled for ESU and host SQL Server 2014 instances when SQL Server 2014 ESU program starts
42
-
-->
42
+
Pre-release Notes:
43
+
- Arc SQL Server | Allow the AG inventory feature for all license types | GA
44
+
- Always On availability groups inventory feature is available for all license type
45
+
- Arc SQL Server | Allow applying physical core license to physical machines | GA
Copy file name to clipboardExpand all lines: articles/azure-arc/servers/manage-vm-extensions.md
+47-51Lines changed: 47 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: VM extension management with Azure Arc-enabled servers
3
3
description: Azure Arc-enabled servers can manage deployment of virtual machine extensions that provide post-deployment configuration and automation tasks with non-Azure VMs.
4
-
ms.date: 05/17/2024
4
+
ms.date: 09/04/2024
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -29,9 +29,9 @@ Azure Arc-enabled servers enables you to deploy, remove, and update Azure VM ext
29
29
30
30
Azure Arc-enabled servers VM extension support provides the following key benefits:
31
31
32
-
- Collect log data for analysis with [Logs in Azure Monitor](../../azure-monitor/logs/data-platform-logs.md) by enabling the Log Analytics agent VM extension. Log Analytics makes it useful for doing complex analysis across log data from different kinds of sources.
32
+
- Collect log data for analysis with [Logs in Azure Monitor](../../azure-monitor/logs/data-platform-logs.md) by enabling the Azure Monitor agent VM extension. Log data analysis makes it useful for doing complex analysis across log data from different kinds of sources.
33
33
34
-
- With [VM insights](../../azure-monitor/vm/vminsights-overview.md), it analyzes the performance of your Windows and Linux VMs, and monitors their processes and dependencies on other resources and external processes. This is achieved through enabling both the Log Analytics agent and Dependency agent VM extensions.
34
+
- With [VM insights](../../azure-monitor/vm/vminsights-overview.md), it analyzes the performance of your Windows and Linux VMs, and monitors their processes and dependencies on other resources and external processes. This is achieved through enabling both the Azure Monitor agent and Dependency agent VM extensions.
35
35
36
36
- Download and execute scripts on hybrid connected machines using the Custom Script Extension. This extension is useful for post deployment configuration, software installation, or any other configuration or management tasks.
37
37
@@ -61,7 +61,6 @@ Arc-enabled servers support moving machines with one or more VM extensions insta
61
61
|Microsoft Defender for Cloud integrated vulnerability scanner |Qualys |WindowsAgent.AzureSecurityCenter |[Microsoft Defender for Cloud’s integrated vulnerability assessment solution for Azure and hybrid machines](../../security-center/deploy-vulnerability-assessment-vm.md)|
62
62
|Microsoft Antimalware extension |Microsoft.Azure.Security |IaaSAntimalware |[Microsoft Antimalware extension for Windows](/azure/virtual-machines/extensions/iaas-antimalware-windows)|
|Azure Monitor Agent |Microsoft.Azure.Monitor |AzureMonitorLinuxAgent |[Install the Azure Monitor agent](../../azure-monitor/agents/azure-monitor-agent-manage.md)|
@@ -106,11 +104,9 @@ To deploy an extension to Arc-enabled servers, a user requires the following per
106
104
107
105
The role **Azure Connected Machine Resource Administrator** includes the permissions required to deploy extensions, however it also includes permission to delete Arc-enabled server resources.
108
106
109
-
### Log Analytics VM extension
107
+
### Azure Monitor agent VM extension
110
108
111
-
The Log Analytics agent VM extension for Linux requires Python 2.x is installed on the target machine.
112
-
113
-
Before you install the extension we suggest you review the [deployment options for the Log Analytics agent](concept-log-analytics-extension-deployment.md) to understand the different methods available and which meets your requirements.
109
+
Before you install the extension we suggest you review the [deployment options for the Azure Monitor agent](concept-log-analytics-extension-deployment.md) to understand the different methods available and which meets your requirements.
114
110
115
111
### Azure Key Vault VM extension
116
112
@@ -146,52 +142,52 @@ The following extensions are available for Windows and Linux machines:
146
142
147
143
### Windows extension availability
148
144
149
-
|Operating system |Azure Monitor agent |Log Analytics agent |Dependency VM Insights |Qualys |Custom Script |Key Vault |Hybrid Runbook |Antimalware Extension |Windows Admin Center |
|Red Hat Enterprise Linux Server 8 |X ||X |X ||X |X |
179
+
|Red Hat Enterprise Linux Server 7 |X |X |X |X ||X |X |
180
+
|Red Hat Enterprise Linux Server 6 ||X |X |||X ||
181
+
|SUSE Linux Enterprise Server 15.2 |X ||X |X |X ||X |
182
+
|SUSE Linux Enterprise Server 15.1 |X ||X |X |X |X |X |
183
+
|SUSE Linux Enterprise Server 15 SP1 |X |X |X |X |X |X |X |
184
+
|SUSE Linux Enterprise Server 15 |X |X |X |X |X |X |X |
185
+
|SUSE Linux Enterprise Server 15 SP5 |X |X |X |X ||X |X |
190
186
|SUSE Linux Enterprise Server 12 SP5 |X |X |X |X |X ||X |X |
191
-
|Ubuntu 20.04 LTS |X |X |X |X |X ||X |X |
192
-
|Ubuntu 18.04 LTS |X |X |X |X |X |X |X |X |
193
-
|Ubuntu 16.04 LTS |X |X |X |X |||X |X |
194
-
|Ubuntu 14.04 LTS ||X ||X |||X ||
187
+
|Ubuntu 20.04 LTS |X |X |X |X ||X |X |
188
+
|Ubuntu 18.04 LTS |X |X |X |X |X |X |X |
189
+
|Ubuntu 16.04 LTS |X |X |X |||X |X |
190
+
|Ubuntu 14.04 LTS |||X |||X ||
195
191
196
192
For the regional availabilities of different Azure services and VM extensions available for Azure Arc-enabled servers, [refer to Azure Global's Product Availability Roadmap](https://global.azure.com/product-availability/roadmap).
0 commit comments