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
description: Learn about how to use stretched clusters for Azure VMware Solution.
4
4
ms.topic: concept-article
5
5
ms.service: azure-vmware
6
-
ms.date: 12/24/2024
6
+
ms.date: 1/8/2026
7
7
ms.custom: references_regions, engagement-fy24
8
8
# Customer intent: "As a cloud architect, I want to design a vSAN stretched cluster for Azure VMware Solution, so that I can enhance application availability and ensure resilience against Availability Zone failures while managing my infrastructure efficiently."
9
9
---
@@ -116,7 +116,10 @@ No. A stretched cluster is created between two availability zones, while the thi
116
116
- NSX Edge Scale-OUT to add additional NSX Edges is not supported at this time.
117
117
- Open a [support ticket](https://rc.portal.azure.com/#create/Microsoft.Support) from the Azure portal for the following scenarios (be sure to select **Stretched Clusters** as a **Problem Type**):
118
118
- Connect a private cloud to a stretched cluster private cloud.
119
-
- Connect two stretched cluster private clouds in a single region.
119
+
- Connect two stretched cluster private clouds.
120
+
121
+
>[!NOTE]
122
+
>Azure VMware Solution interconnect between stretched cluster private clouds is supported only when both stretched clusters are either hosted within the same pod set or have no common pod between them. It is not supported if the private cloud share only one common pod.
120
123
121
124
### What kind of latencies should I expect between the availability zones (AZs)?
title: CycleCloud Workspace for Slurm - Release Notes 2025.12.01
3
+
description: These release notes for Azure CycleCloud Workspace for Slurm 2025.12.01 summarize new features and bug fixes included in the release.
4
+
author: abatallas
5
+
ms.date: 12/18/2025
6
+
ms.author: padmalathas
7
+
---
8
+
9
+
# CycleCloud Workspace for Slurm version 2025.12.01
10
+
11
+
Azure CycleCloud Workspace for Slurm 2025.12.01 was released as General Audience. This article provides you with information about:
12
+
13
+
* Recent releases
14
+
* Previews underway with known limitations (if applicable)
15
+
* Known issues
16
+
* Deprecated functionality (if applicable)
17
+
18
+
The following release notes identify the new features and the open issues for the 2025.09.15 release of Azure CycleCloud Workspace for Slurm.
19
+
20
+
The release notes are continuously updated. Open known issues that require a workaround are added when they're discovered. Carefully review the information in the release notes before deploying Azure CycleCloud Workspace for Slurm.
21
+
22
+
This release corresponds to the software version:
23
+
24
+
-**CycleCloud Workspace for Slurm version 2025.12.01**
25
+
26
+
## What's new in CycleCloud Workspace for Slurm version 2025.12.01?
27
+
28
+
Azure CycleCloud Workspace for Slurm is updated regularly. Stay up to date with the latest announcements.
29
+
30
+
This release contains the following new features:
31
+
32
+
* Use of CycleCloud Marketplace Image 8.8.1
33
+
* Removal of all NVMe and Pyxis-related cluster-init scripts (now native to CycleCloud)
34
+
* Microsoft Entra ID single sign-on
35
+
* Support for Microsoft Entra ID for single sign-on
36
+
* Utility script for creating a Microsoft Entra ID application registration for use with CCW
37
+
* Utility script for updating an existing application registration following a successful CCW deployment
38
+
* Open OnDemand
39
+
* Support for Open OnDemand 4.0.8
40
+
* Inclusion of Open OnDemand cluster template in CycleCloud for possible future use
41
+
* Admin user owns copy of Open OnDemand cluster parameters found in home directory if applicable
42
+
* Support for multiple user domains
43
+
* Support for monitoring with existing instances of Azure Monitor workspaces
44
+
* Larger subnet sizes in auto-created virtual networks when using Azure Managed Lustre
45
+
* Support for Ubuntu 24.04 and Alma Linux 9 on all cluster nodes
46
+
* Support for Slurm 25.05.2, deprecation of support for 23.11.10 and 24.05.4
47
+
48
+
## Known issues in this release
49
+
50
+
-**Open OnDemand**: IP addresses are erroneously marked as invalid input in the FQDN field of the Open OnDemand section of the Marketplace UI. To work around this issue, leave the FQDN field blank, uncheck "Start Cluster," and then add the desired IP in the FQDN field of the Open OnDemand cluster's settings in the CycleCloud web UI.
51
+
-**Azure US Gov Only**: Marketplace deployment validation fails due to an incorrect API version. To mitigate this issue, refer: [How to deploy a CycleCloud Workspace for Slurm environment using the CLI](../../how-to/ccws/deploy-with-cli.md).
Copy file name to clipboardExpand all lines: articles/data-factory/connector-microsoft-fabric-lakehouse.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -573,6 +573,8 @@ To copy data to Microsoft Fabric Lakehouse using Microsoft Fabric Lakehouse Tabl
573
573
574
574
>[!Note]
575
575
> Data is written to Lakehouse Table in V-Order by default. For more information, go to [Delta Lake table optimization and V-Order](/fabric/data-engineering/delta-optimization-and-v-order?tabs=sparksql#what-is-v-order).
576
+
>
577
+
> For more details on Delta Lake interoperability and supported behaviors across pipelines, go to [Delta Lake table format interoperability](/fabric/fundamentals/delta-lake-interoperability#delta-lake-features-and-fabric-experiences).
0 commit comments