Here are some frequently asked questions (FAQs) and answers for Service Fabric managed clusters.
General
What are Service Fabric managed clusters?
Service Fabric managed clusters are an evolution of the Service Fabric cluster resource model designed to make it easier to deploy and manage clusters. A Service Fabric managed cluster uses the Azure Resource Manager encapsulation model so that a user only needs to define and deploy a single cluster resource compared to the many independent resources that they must deploy today (Virtual Machine Scale Set, Load Balancer, IP, and more).
What regions are supported?
Service Fabric managed clusters are supported in all cloud regions.
Can I do an in-place migration of my existing Service Fabric cluster to a managed cluster resource?
No, you need to create a new Service Fabric cluster resource to use the new Service Fabric managed cluster resource type.
Is there an additional cost for Service Fabric managed clusters?
No, there's no additional cost associated with a Service Fabric managed cluster beyond the cost of the underlying compute, storage, and networking resources that are required for the cluster.
Is there a new SLA introduced by the Service Fabric managed cluster resource?
The SLA doesn't change from the current Service Fabric resource model.
What's the difference between a Basic, and Standard SKU cluster?
Basic SKU clusters are intended to be used for testing and pre production environments with support for minimal configuration change. A Standard SKU cluster allows users to configure the cluster to specifically meet their needs. For more information, see Service Fabric managed cluster SKUs.
Where can I see planned features or suggest one?
Please see our GitHub project for managed clusters
Cluster Deployment and Management
I run custom script extensions on my Virtual Machine Scale Set, can I continue to do that with a managed Service Fabric resource?
Yes, you can specify VM extensions on managed cluster node types. For more information, see Add a scale set extension to a Service Fabric managed cluster node type.
I want to have an internal-only load balancer, is that possible?
Yes, you can configure internal-only load balancer. See Configure network settings for Service Fabric managed clusters
Can I change the Microsoft Entra tenant after initial deployment?
No, you need to create a new Service Fabric managed cluster resource.
Can I transfer my subscription to a different Microsoft Entra tenant?
No, you need to create a new Service Fabric managed cluster resource after the subscription has been transferred to a different Microsoft Entra tenant.
Can I move/migrate my cluster between Microsoft Entra tenants?
No, you need to create a new Service Fabric managed cluster resource under the new tenant.
Can I move/migrate my cluster between subscriptions?
No, you need to create a new Service Fabric managed cluster resource under the new subscription.
Can I move/migrate my cluster or cluster resources to other resource groups or rename them?
No, you need to create a new Service Fabric managed cluster resource under the new resource group/name.
I want to enable IPv6, is that possible?
I want to use an existing VNet for a Service Fabric managed cluster, can I do that?
Can I autoscale my cluster?
Autoscaling is not currently supported.
Can I deploy my cluster across availability zones?
Yes, Service Fabric managed clusters which span availability zones are supported in Azure regions which support availability zones. For more information, see Service Fabric managed clusters across availability zones.
Can I deploy stateless node types on a Service Fabric managed cluster?
Yes, Service Fabric managed clusters support stateless node types for any secondary node types. For more information, see Service Fabric managed cluster stateless node types
Can I select between automatic and manual upgrades for my cluster runtime?
Yes, you can select between automatic and manual upgrades. For more information, see cluster upgrades.
Can I set up maintenance control for my cluster?
Yes, you can enable maintenance control
Why do I get 'Your connection isn't private' when connecting to Service Fabric Explorer (SFX) on a managed cluster?
Connecting to a Service Fabric Explorer (SFX) endpoint on a managed cluster will result in a certificate error 'NET::ERR_CERT_AUTHORITY_INVALID' regardless of certificate being used or cluster configuration. This is because the cluster nodes are using the managed 'cluster' certificate when binding FabricGateway (19000) and FabricHttpGateway (19080) TCP ports and is by design.
Can I manually make changes to a managed cluster's resources?
No, manually making changes to a managed cluster's resource isn't supported.
Applications
Is there a local development experience for Service Fabric managed clusters?
The local development experience remains unchanged from existing Service Fabric clusters. For more information, see Set up your development environment for more details on the local development experience.
Can I deploy my applications as an Azure Resource Manager resource?
Yes. Support has been added to deploy applications as an Azure Resource Manager resource (in addition to deployment using PowerShell and CLI). To get started, see Deploy a Service Fabric managed cluster application using ARM template.
Can I deploy applications with managed identities?
Yes, applications with managed identities can be deployed to a Service Fabric managed cluster. For more information see, Configure and use applications with managed identity on a Service Fabric managed cluster.