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/api-management/api-management-advanced-policies.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
@@ -858,7 +858,7 @@ This policy can be used in the following policy [sections](./api-management-howt
858
858
859
859
## <aname="SetHttpProxy"></a> Set HTTP proxy
860
860
861
-
The `proxy` policy allows you to route requests forwarded to backends via an HTTP proxy. Only HTTP (not HTTPS) is supported between the gateway and the proxy. Basic and NTLM authentication only.
861
+
The `proxy` policy allows you to route requests forwarded to backends via an HTTP proxy. Only HTTP (not HTTPS) is supported between the gateway and the proxy. Basic and NTLM authentication only. To route the send-request via HTTP proxy, you must place the set HTTP proxy policy inside the send-request policy block.
Copy file name to clipboardExpand all lines: articles/app-service/configure-connect-to-azure-storage.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
@@ -37,7 +37,7 @@ This guide shows how to mount Azure Storage Files as a network share in a Window
37
37
- Make static content like video and images readily available for your App Service app.
38
38
- Write application log files or archive older application log to Azure File shares.
39
39
- Share content across multiple apps or with other Azure services.
40
-
- Mount Azure Storage in a Windows container in a Standard tier or higher plan, including Isolated ([App Service environment v3](environment/overview.md)).
40
+
- Mount Azure Storage in a Windows container, including Isolated ([App Service environment v3](environment/overview.md)).
41
41
42
42
The following features are supported for Windows containers:
description: Learn about the networking requirements for using the Connected Machine agent for Azure Arc-enabled servers.
4
-
ms.date: 09/09/2022
4
+
ms.date: 09/29/2022
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -55,6 +55,7 @@ The table below lists the URLs that must be available in order to install and us
55
55
|`guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com`|Notification service for extension and connectivity scenarios|Always| Public |
56
56
|`azgn*.servicebus.windows.net`|Notification service for extension and connectivity scenarios|Always| Public |
57
57
|`*.servicebus.windows.net`|For Windows Admin Center and SSH scenarios|If using SSH or Windows Admin Center from Azure|Public|
58
+
|`*.waconazure.com`|For Windows Admin Center connectivity|If using Windows Admin Center|Public|
58
59
|`*.blob.core.windows.net`|Download source for Azure Arc-enabled servers extensions|Always, except when using private endpoints| Not used when private link is configured |
59
60
|`dc.services.visualstudio.com`|Agent telemetry|Optional| Public |
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,9 @@ To enable system-assigned managed identity in the Azure portal:
79
79
80
80
For information on enabling system-assigned managed identity through Azure CLI or PowerShell, check out more information on [using managed identities with Azure Functions](../app-service/overview-managed-identity.md?tabs=dotnet&toc=%2fazure%2fazure-functions%2ftoc.json#add-a-system-assigned-identity).
81
81
82
+
> [!TIP]
83
+
> For user-assigned managed identity, switch to the User Assigned tab. Click Add and select a Managed Identity. For more information on creating user-assigned managed identity, see the [Manage user-assigned managed identities](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md).
84
+
82
85
83
86
## Grant SQL database access to the managed identity
84
87
@@ -114,8 +117,11 @@ In the application settings of our Function App the SQL connection string settin
114
117
115
118
*testdb* is the name of the database we're connecting to and *demo.database.windows.net* is the name of the server we're connecting to.
116
119
120
+
>[!TIP]
121
+
>For user-assigned managed identity, use `Server=demo.database.windows.net; Authentication=Active Directory Managed Identity; User Id=ClientIdOfManagedIdentity; Database=testdb`.
122
+
117
123
## Next steps
118
124
119
125
- [Read data from a database (Input binding)](./functions-bindings-azure-sql-input.md)
120
126
- [Save data to a database (Output binding)](./functions-bindings-azure-sql-output.md)
121
-
- [Review ToDo API sample with Azure SQL bindings](/samples/azure-samples/azure-sql-binding-func-dotnet-todo/todo-backend-dotnet-azure-sql-bindings-azure-functions/)
127
+
- [Review ToDo API sample with Azure SQL bindings](/samples/azure-samples/azure-sql-binding-func-dotnet-todo/todo-backend-dotnet-azure-sql-bindings-azure-functions/)
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/app-insights-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ To use the SDK, you install a small instrumentation package in your app and then
60
60
61
61
### [.NET](#tab/net)
62
62
63
-
Integrated Auto-instrumentation is available for [Azure App Service .NET](azure-web-apps-net.md), [Azure App Service .NET Core](azure-web-apps-net-core.md), [Azure Functions](../../azure-functions/functions-monitoring.md#monitor-executions-in-azure-functions), and [Azure Virtual Machines](azure-vm-vmss-apps.md).
63
+
Integrated Auto-instrumentation is available for [Azure App Service .NET](azure-web-apps-net.md), [Azure App Service .NET Core](azure-web-apps-net-core.md), [Azure Functions](../../azure-functions/functions-monitoring.md), and [Azure Virtual Machines](azure-vm-vmss-apps.md).
64
64
65
65
[Azure Monitor Application Insights Agent](status-monitor-v2-overview.md) is available for workloads running in on-premises virtual machines.
66
66
@@ -72,9 +72,9 @@ A preview [Open Telemetry](opentelemetry-enable.md?tabs=net) offering is also av
72
72
73
73
### [Java](#tab/java)
74
74
75
-
Auto-instrumentation is available for any environment using [Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](java-in-process-agent.md).
75
+
Integrated Auto-Instrumentation is available for Java Apps hosted on [Azure App Service](azure-web-apps-java.md) and [Azure Functions](monitor-functions.md).
76
76
77
-
Integrated Auto-Instrumentation is available for Java Apps hosted on [Azure App Service](azure-web-apps-java.md) and [Azure Functions](monitor-functions.md#distributed-tracing-for-java-applications-public-preview).
77
+
Auto-instrumentation is available for any environment using [Azure Monitor OpenTelemetry-based auto-instrumentation for Java applications](java-in-process-agent.md).
@@ -108,7 +111,7 @@ If you selected to create a new backup policy, fill in the policy settings.
108
111
2. In **Backup schedule**, specify when backups should be taken. You can take daily or weekly backups for Azure VMs.
109
112
3. In **Instant Restore**, specify how long you want to retain snapshots locally for instant restore.
110
113
* When you restore, backed up VM disks are copied from storage, across the network to the recovery storage location. With instant restore, you can leverage locally stored snapshots taken during a backup job, without waiting for backup data to be transferred to the vault.
111
-
* You can retain snapshots for instant restore for between one to five days. Two days is the default setting.
114
+
* You can retain snapshots for instant restore for between one to five days. The default setting is *two days*.
112
115
4. In **Retention range**, specify how long you want to keep your daily or weekly backup points.
113
116
5. In **Retention of monthly backup point** and **Retention of yearly backup point**, specify whether you want to keep a monthly or yearly backup of your daily or weekly backups.
114
117
6. Select **OK** to save the policy.
@@ -118,13 +121,14 @@ If you selected to create a new backup policy, fill in the policy settings.
> Azure Backup doesn't support automatic clock adjustment for daylight-saving changes for Azure VM backups. As time changes occur, modify backup policies manually as required.
124
+
>- Azure Backup doesn't support automatic clock adjustment for daylight-saving changes for Azure VM backups. As time changes occur, modify backup policies manually as required.
125
+
>- If you want hourly backups, then you can configure *Enhanced backup policy*. For more information, see [Back up an Azure VM using Enhanced policy](backup-azure-vms-enhanced-policy.md#create-an-enhanced-policy-and-configure-vm-backup).
122
126
123
127
## Trigger the initial backup
124
128
125
129
The initial backup will run in accordance with the schedule, but you can run it immediately as follows:
126
130
127
-
1.Navigate to Backup center and select the **Backup Instances** menu item.
131
+
1.Go to the Backup center and select the **Backup Instances** menu item.
128
132
1. Select **Azure Virtual machines** as the **Datasource type**. Then search for the VM that you have configured for backup.
129
133
1. Right-click the relevant row or select the more icon (…), and then click **Backup Now**.
130
134
1. In **Backup Now**, use the calendar control to select the last day that the recovery point should be retained. Then select **OK**.
0 commit comments