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-netapp-files/configure-cache-volumes.md
+49-13Lines changed: 49 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,22 +125,34 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
125
125
126
126
## Create a cache volume
127
127
128
-
1. Initiate the cache volume creation using the PUT caches API call.
128
+
1. Initiate the cache volume creation using the PUT caches API call. For information about cache operations, see [API documentation](/rest/api/netapp/caches?view=rest-netapp-2025-09-01-preview&preserve-view=true).
129
129
130
-
2. Monitor if the cache state is available for cluster peering with a GET request.
130
+
```
131
+
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
132
+
```
133
+
2. Monitor if the cache state is available for cluster peering with a GET request.
131
134
132
-
When the `cacheState = ClusterPeeringOfferSent`, execute the POST `listPeeringPassphrases` call to obtain the command and passphrase necessary to complete the cluster peering.
133
-
134
-
Example `listPeeringPassphrases` output:
135
+
```
136
+
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
When the `cacheState = ClusterPeeringOfferSent`, execute the POST `listPeeringPassphrases` call to obtain the command and passphrase necessary to complete the cluster peering.
143
140
141
+
Example listPeeringPassprhases:
142
+
143
+
```
144
+
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}/listPeeringPassphrases?api-version=2025-09-01-preview
Execute the `clusterPeeringCommand` on the ONTAP system that contains the external origin volume and when prompted, enter the clusterPeeringPassphrase.
145
157
146
158
> [!NOTE]
@@ -157,6 +169,9 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
157
169
158
170
3. Monitor if the cache state is available for storage VM peering using a GET request.
159
171
172
+
```
173
+
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
174
+
```
160
175
When the `cacheState = VserverPeeringOfferSent`, go to the ONTAP system that contains the external origin volume and execute the `vserver peer show` command until an entry appears where the remote storage VM displays the `<value of the -peer-vserver in the vserverPeeringCommand>`. The peer state shows "pending."
161
176
162
177
Execute the `vserverPeeringCommand` on the ONTAP system that contains the external origin volume. The peer state should transition to "peered."
@@ -176,6 +191,9 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
176
191
# [NFS](#tab/NFS)
177
192
178
193
```
194
+
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
195
+
196
+
Body:
179
197
{
180
198
"location": "westus",
181
199
"zones": [
@@ -223,6 +241,9 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
223
241
# [SMB](#tab/SMB)
224
242
225
243
```
244
+
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
245
+
246
+
Body:
226
247
{
227
248
"zones": [
228
249
"2"
@@ -252,6 +273,9 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
252
273
# [Dual-protocol](#tab/DualProtocol)
253
274
254
275
```
276
+
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
277
+
278
+
Body:
255
279
{
256
280
"zones": ["2"],
257
281
"location": "southcentralus",
@@ -299,6 +323,9 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
299
323
# [LDAP](#tab/LDAP)
300
324
301
325
```
326
+
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/caches/{cacheName}?api-version=2025-09-01-preview
327
+
328
+
Body:
302
329
{
303
330
"location": "westus",
304
331
"zones": [
@@ -351,15 +378,24 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
351
378
Example patch request body to update a cache volume:
Copy file name to clipboardExpand all lines: articles/backup/sap-hana-backup-support-matrix.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: SAP HANA Backup support matrix
3
3
description: In this article, learn about the supported scenarios and limitations when you use Azure Backup to back up SAP HANA databases on Azure VMs.
4
4
ms.topic: reference
5
-
ms.date: 12/09/2025
5
+
ms.date: 12/11/2025
6
6
ms.custom: references_regions
7
7
ms.service: azure-backup
8
8
author: AbhishekMallick-MS
@@ -36,7 +36,7 @@ Azure Backup supports the backup of SAP HANA databases to Azure. This article su
36
36
|**Restore types**| Refer to the SAP HANA Note [1642148](https://launchpad.support.sap.com/#/notes/1642148) to learn about the supported restore types ||
37
37
|**Cross Subscription Restore**| Supported via the Azure portal and Azure CLI. [Learn more](sap-hana-database-restore.md#cross-subscription-restore). ||
38
38
|**Number of full backups per day**| One scheduled backup. <br><br> Three on-demand backups. <br><br> We recommend not to trigger more than three backups per day. However, to allow user retries in case of failed attempts, hard limit for on-demand backups is set to nine attempts. |
39
-
|**HANA deployments**| HANA System Replication (HSR) ||
39
+
|**HANA deployments**| HANA System Replication (HSR) <br><br> HANA Scale-out system i.e one HANA system distributed across multiple nodes(PREVIEW)||
40
40
|**Special configurations**|| SAP HANA + Dynamic Tiering <br> Cloning through LaMa |
41
41
|**Compression**| You can enable HANA Native compression via the Backup policy. [See the SAP HANA document](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/86943e9f8d5343c59577755edff8296b.html). ||
42
42
|**Multi-streaming backup**| You can increase your streaming backup throughput from *420 MBps* to *1.5 GBps*. [Learn more](#support-for-multistreaming-data-backups). ||
@@ -88,6 +88,9 @@ The following table lists the required parameters for adding/removing SAP HANA i
88
88
|**Add an instance**|`--sid`| SAP HANA database instance that you want to protect. <br><br> By default, the first instance is selected. |`./msawb-plugin-config-com-sap-hana.sh --add --sid HXE` <br><br> Or <br><br> `./msawb-plugin-config-com-sap-hana.sh --sid HXE` <br><br> (Default mode is `add` for the script.) <br><br> After you add instances, registration needs to be done on recovery services vault. If a new instance is added later, re-registration is required.|
89
89
|**Remove an instance**|`--sid`| SAP HANA database instance that you want to remove protection. <br><br> **SID** is a mandate parameter for remove. |`./msawb-plugin-config-com-sap-hana.sh --remove --sid HXE`|
90
90
91
+
## Support for HANA Scale-out (PREVIEW)
92
+
Backup for HANA systems distributed across multiple nodes i.e. HANA Scale-out is now available in PREVIEW. Reach out to [email protected] to gain access to the preview experience.
93
+
91
94
## Next steps
92
95
93
96
- Back up SAP HANA databases on Azure VMs using [Azure portal](backup-azure-sap-hana-database.md) and [Azure CLI](tutorial-sap-hana-backup-cli.md).
Copy file name to clipboardExpand all lines: articles/expressroute/cross-connections-api-development.md
+158Lines changed: 158 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -389,6 +389,164 @@ Once you receive the ExpressRoute service key from the target customer, follow t
389
389
"status": "Succeeded"
390
390
}
391
391
```
392
+
### To validate the advertised public prefixes (Public Preview)
393
+
6.**(Optional) GET expressRouteCrossConnection to verify Microsoft Peering advertised prefixes** If you allow customers to advertise your public IP addresses over Microsoft Peering, you can obtain the Validation ID required to authorize their prefix usage.
394
+
395
+
> [!NOTE]
396
+
> When customer advertises public prefixes over BGP, Microsoft verifies the authority to announce them by validating a signed digital certificate against RIR or IRR records. The prefixes may be owned by the customer, or leased from your organization. See the [authorization requirements](expressroute-howto-routing-portal-resource-manager.md) for more details
397
+
398
+
```
399
+
GET /subscriptions/<ProviderManagementSubscription>/resourceGroups/CrossConnection-EUAPTest/providers/Microsoft.Network/expressRouteCrossConnections/bbbb1b1b-cc2c-dd3d-ee4e-ffffff5f5f5f/peerings/MicrosoftPeering?api-version=2024-05-01 HTTP/1.1
C:\Users\Admin\Documents\Expressroute\Partner APIs\ARMClient-master\ARMClient-master>armclient get https://management.azure.com/subscriptions/<ProviderManagementSubscription>/providers/Microsoft.Network/locations/eastus2euap/operations/eeee4efe-ff5f-aa6a-bb7b-cccccc8c8c8c?api-version=2018-02-01
457
+
{
458
+
"status": "Succeeded"
459
+
}
460
+
```
461
+
7.**(Optional) PUT expressRouteCrossConnection to validate Microsoft Peering advertised prefixes** If you allow customers to advertise your public IP addresses over Microsoft Peering, you can configure the signature to automatically validate the advertised prefixes.
462
+
463
+
```
464
+
PUT /subscriptions/<ProviderManagementSubscription>/resourceGroups/CrossConnection-EUAPTest/providers/Microsoft.Network/expressRouteCrossConnections/bbbb1b1b-cc2c-dd3d-ee4e-ffffff5f5f5f/peerings/MicrosoftPeering?api-version=2018-02-01 HTTP/1.1
C:\Users\Admin\Documents\Expressroute\Partner APIs\ARMClient-master\ARMClient-master>armclient get https://management.azure.com/subscriptions/<ProviderManagementSubscription>/providers/Microsoft.Network/locations/eastus2euap/operations/eeee4efe-ff5f-aa6a-bb7b-cccccc8c8c8c?api-version=2018-02-01
546
+
{
547
+
"status": "Succeeded"
548
+
}
549
+
```
392
550
## REST API
393
551
394
552
See [ExpressRoute CrossConnections REST API](/rest/api/expressroute/expressroutecrossconnections) for REST API documentation.
Copy file name to clipboardExpand all lines: articles/logic-apps/connectors/sap.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1080,9 +1080,13 @@ Based on whether you have a Consumption workflow in multitenant Azure Logic Apps
1080
1080
1081
1081
## Enable SAP client library (NCo) logging and tracing (built-in connector only)
1082
1082
1083
-
When you have to investigate any problems with this component, you can set up custom text file-based NCo tracing, which SAP or Microsoft support might request from you. However, even without enabling NCo tracing, you can find the log (.log) files at the following location: `C:\home\site\wwwroot`.
1083
+
When you have to investigate any problems with this component, you can set up custom text file-based NCo tracing, which SAP or Microsoft support might request from you. By default, the tracing capability is disabled because tracing might negatively affect performance and quickly consume the application host's storage space.
1084
1084
1085
-
By default, the tracing capability is disabled because tracing might negatively affect performance and quickly consume the application host's storage space. To enable tracing at the application level, add the following settings:
1085
+
> [!NOTE]
1086
+
>
1087
+
> Error logging is enabled even without enabling NCo tracing. To find the error log (.log) files, go to the following default location: `C:\home\site\wwwroot`. If the app setting named **SAP_RFC_TRACE_DIRECTORY** specifies a different location, the error logs are stored there instead.
1088
+
1089
+
To enable tracing at the application level, add the following settings:
1086
1090
1087
1091
1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
Copy file name to clipboardExpand all lines: articles/sap/business-process-solutions/deploy-workload-item.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,10 +69,10 @@ To deploy Business process solutions, you need:
69
69
70
70
### Create Microsoft Fabric workspace
71
71
72
-
Before proceeding with either manual or automated deployment of Enterprise Insights you need to create a Microsoft Fabric workspace. Follow the steps below to set up your workspace:
72
+
Before proceeding with deployment of Business Process Solutions you need to create a Microsoft Fabric workspace. Use the following steps to set up your workspace:
73
73
74
74
1. Open Microsoft Fabric: [Power BI](https://app.powerbi.com/).
75
-
2. From the left menu choose **Workspaces** and choose **New workspace**.
75
+
2. From the left menu, choose **Workspaces** and choose **New workspace**.
76
76
:::image type="content" source="./media/deploy-workload-item/new-workspace.jpg" alt-text="Screenshot showing how to create a new Microsoft Fabric workspace." lightbox="./media/deploy-workload-item/new-workspace.jpg":::
77
77
3. Provide the Name of the workspace. Open the Advanced settings and choose **Large Semantic Model Storage Format**. Confirm by clicking **Apply**.
78
78
:::image type="content" source="./media/deploy-workload-item/workspace-details.jpg" alt-text="Screenshot showing the new workspace details configuration." lightbox="./media/deploy-workload-item/workspace-details.jpg":::
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments