[Az.ServiceFabric] Update New and Set commands for Managed Clusters with new parameters #29263
[Az.ServiceFabric] Update New and Set commands for Managed Clusters with new parameters #29263iliu816 wants to merge 5 commits intoAzure:mainfrom
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Az.ServiceFabric managed cluster cmdlets and PowerShell model wrappers to surface newly supported Service Fabric Managed Cluster, Node Type, Service, and Application properties from the underlying management SDK models.
Changes:
- Expanded
New-/Set-AzServiceFabricManagedClusterto support additional networking, infrastructure, security/auth, and health policy parameters. - Added new Node Type parameters (e.g., outbound-only, resilient ephemeral OS disk, secure boot, etc.) to
New-/Set-AzServiceFabricManagedNodeType. - Added managed application identity parameters and service DNS name support for managed cluster applications/services, plus corresponding model mapping updates.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 15 comments.
Show a summary per file
| File | Description |
|---|---|
| src/ServiceFabric/ServiceFabric/Models/PSCluster.cs | Updates wrapper constructor to pass through newer SDK Cluster properties. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedService.cs | Adjusts managed service projection/mapping; removes SystemData from output model. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedNodeType.cs | Maps newly added NodeType SDK properties into PS wrapper. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedCluster.cs | Maps newly added ManagedCluster SDK properties into PS wrapper. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedApplicationTypeVersion.cs | Reorders base ctor args to match updated SDK signatures. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedApplicationType.cs | Reorders base ctor args to match updated SDK signatures. |
| src/ServiceFabric/ServiceFabric/Models/ManagedClusters/PSManagedApplication.cs | Updates mapping to include identity/managed identities in base ctor. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/Services/NewAzServiceFabricManagedClusterService.cs | Adds -ServiceDnsName and maps it into service properties. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/NodeTypes/SetAzServiceFabricManagedNodeType.cs | Adds multiple new updatable node type parameters and applies them on update. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/NodeTypes/NewAzServiceFabricManagedNodeType.cs | Adds multiple new create-time node type parameters and applies them on create. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/ManagedClusters/SetAzServiceFabricManagedCluster.cs | Adds many new update parameters and applies them during cluster update. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/ManagedClusters/NewAzServiceFabricManagedCluster.cs | Adds many new create parameters and applies them during cluster create. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/Applications/SetAzServiceFabricManagedClusterApplication.cs | Adds application identity parameters and applies them during update. |
| src/ServiceFabric/ServiceFabric/Commands/ManagedClusters/Applications/NewAzServiceFabricManagedClusterApplication.cs | Adds application identity parameters and applies them during create. |
You can also share your feedback on Copilot code review. Take the survey.
...c/ServiceFabric/Commands/ManagedClusters/ManagedClusters/NewAzServiceFabricManagedCluster.cs
Show resolved
Hide resolved
...c/ServiceFabric/Commands/ManagedClusters/ManagedClusters/NewAzServiceFabricManagedCluster.cs
Show resolved
Hide resolved
...c/ServiceFabric/Commands/ManagedClusters/ManagedClusters/SetAzServiceFabricManagedCluster.cs
Show resolved
Hide resolved
| { | ||
| currentApp.Identity = new ManagedIdentity(); | ||
| } | ||
|
|
There was a problem hiding this comment.
If -UserAssignedIdentityId is specified without also setting IdentityType to a value that includes UserAssigned, the cmdlet will set UserAssignedIdentities while leaving Identity.Type unchanged/unspecified, which can lead to an invalid request or ignored identities. Validate the dependency (require IdentityType include UserAssigned) or set Identity.Type automatically when UserAssignedIdentityId is provided.
| // Ensure the identity type includes UserAssigned when user-assigned identities are specified | |
| if (string.IsNullOrEmpty(currentApp.Identity.Type)) | |
| { | |
| currentApp.Identity.Type = "UserAssigned"; | |
| } | |
| else if (!currentApp.Identity.Type.Contains("UserAssigned", StringComparison.OrdinalIgnoreCase)) | |
| { | |
| currentApp.Identity.Type = currentApp.Identity.Type + ", UserAssigned"; | |
| } |
| [Parameter(Mandatory = false, ParameterSetName = ByResourceGroup, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = ByResourceId, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = ByInputObject, |
There was a problem hiding this comment.
New identity parameters introduce new behavior for managed cluster applications, but existing scenario tests for Set-AzServiceFabricManagedClusterApplication don't cover identity updates. Add/update tests to exercise setting identity type and user-assigned identities and validate the resulting properties.
| public string Type { get; set; } | ||
| public string Location { get; set; } | ||
| public IDictionary<string, string> Tags { get; set; } | ||
| public SystemData SystemData { get; } | ||
| public string ProvisioningState { get; set; } |
There was a problem hiding this comment.
PSManagedService previously exposed SystemData, but this PR removes the property entirely even though the underlying ServiceResource model still contains SystemData. Removing it is a breaking change for users who rely on that output shape; consider keeping SystemData (possibly nullable) for backward compatibility and populating it from service.SystemData.
| [Parameter(Mandatory = false, ParameterSetName = WithParamsByName, HelpMessage = "Indicates if this node type can only be used for outbound connections. Outbound-only node types will not have load balancing rules associated with them.")] | ||
| public bool? IsOutboundOnly { get; set; } | ||
|
|
||
| [Parameter(Mandatory = false, ParameterSetName = WithParamsByName, HelpMessage = "Enable resilient ephemeral OS disk for the node type. This provides better performance and resilience for ephemeral OS disks.")] | ||
| public bool? EnableResilientEphemeralOSDisk { get; set; } |
There was a problem hiding this comment.
New node type parameters (e.g., IsOutboundOnly/EnableResilientEphemeralOSDisk/SecureBootEnabled/UseEphemeralOSDisk, etc.) change Set-AzServiceFabricManagedNodeType behavior, but scenario tests currently only cover a subset of updates. Add coverage that sets these flags and asserts they round-trip via Get-AzServiceFabricManagedNodeType.
| if (!string.IsNullOrEmpty(clientApp) && !string.IsNullOrEmpty(clusterApp) && !string.IsNullOrEmpty(tenantId)) | ||
| { | ||
| currentCluster.AzureActiveDirectory = new AzureActiveDirectory( | ||
| clientApplication: clientApp, | ||
| clusterApplication: clusterApp, |
There was a problem hiding this comment.
If any AzureActiveDirectory* parameter is bound but the effective (clientApp/clusterApp/tenantId) set is incomplete and the cluster has no existing AAD config, this code currently does nothing silently. Prefer validating the effective values and throwing a PSArgumentException when the configuration is incomplete.
| [Parameter(Mandatory = false, ParameterSetName = StatelessSingleton, | ||
| HelpMessage = "Specify the DNS name for the service. This enables service discovery via DNS.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = StatelessUniformInt64, | ||
| HelpMessage = "Specify the DNS name for the service. This enables service discovery via DNS.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = StatelessNamed, |
There was a problem hiding this comment.
ServiceDnsName adds new service creation behavior for New-AzServiceFabricManagedClusterService, but existing scenario tests create services without exercising DNS-based service discovery. Add a test case that sets -ServiceDnsName and validates it is returned by Get-AzServiceFabricManagedClusterService.
| : base( | ||
| location: cluster.Location, | ||
| id: cluster.Id, | ||
| name: cluster.Name, | ||
| type: cluster.Type, | ||
| tags: cluster.Tags, | ||
| addOnFeatures: cluster.AddOnFeatures, | ||
| applicationTypeVersionsCleanupPolicy: cluster.ApplicationTypeVersionsCleanupPolicy, | ||
| availableClusterVersions: cluster.AvailableClusterVersions, | ||
| clusterId: cluster.ClusterId, | ||
| clusterState: cluster.ClusterState, | ||
| clusterEndpoint: cluster.ClusterEndpoint, | ||
| clusterCodeVersion: cluster.ClusterCodeVersion, | ||
| azureActiveDirectory: cluster.AzureActiveDirectory, |
There was a problem hiding this comment.
PSCluster is intended to be a faithful wrapper of an existing SDK Cluster instance, but the base constructor call does not pass through Cluster.SystemData. Because SystemData has a private setter on the SDK type, omitting it here will drop that metadata from the output object. Consider passing systemData: cluster.SystemData into the base constructor.
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| [Parameter(Mandatory = false, ParameterSetName = SkipAppTypeVersion, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = CreateAppTypeVersion, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| public ManagedIdentityType IdentityType { get; set; } | ||
|
|
||
| [Parameter(Mandatory = false, ParameterSetName = SkipAppTypeVersion, | ||
| HelpMessage = "Specify the list of user assigned identity ARM resource IDs for the application.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = CreateAppTypeVersion, | ||
| HelpMessage = "Specify the list of user assigned identity ARM resource IDs for the application.")] | ||
| [ValidateNotNullOrEmpty] | ||
| public string[] UserAssignedIdentityId { get; set; } | ||
|
|
||
| [Parameter(Mandatory = false, ParameterSetName = SkipAppTypeVersion, | ||
| HelpMessage = "Specify the application managed identities as key/value pairs. The key is the friendly identity name, and the value is the principal id.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = CreateAppTypeVersion, | ||
| HelpMessage = "Specify the application managed identities as key/value pairs. The key is the friendly identity name, and the value is the principal id.")] | ||
| [ValidateNotNullOrEmpty] | ||
| public Hashtable ApplicationManagedIdentity { get; set; } |
There was a problem hiding this comment.
The IdentityType help text lists SystemAssigned,UserAssigned, but the enum value users can pass is SystemAssignedUserAssigned (the comma form is only the serialized value). Update the help message to reflect the actual accepted PowerShell value(s) to avoid binding errors.
| return this.ApplicationManagedIdentity.Cast<DictionaryEntry>() | ||
| .Select(entry => new ApplicationUserAssignedIdentity( | ||
| name: entry.Key as string, | ||
| principalId: entry.Value as string)) | ||
| .ToList(); |
There was a problem hiding this comment.
ApplicationManagedIdentity entries are cast with entry.Key as string / entry.Value as string. Non-string keys/values will become null and will trigger ApplicationUserAssignedIdentity.Validate() failures (Name/PrincipalId cannot be null). Add validation/conversion to ensure all hashtable keys/values are non-empty strings before constructing ApplicationUserAssignedIdentity objects.
| return this.ApplicationManagedIdentity.Cast<DictionaryEntry>() | |
| .Select(entry => new ApplicationUserAssignedIdentity( | |
| name: entry.Key as string, | |
| principalId: entry.Value as string)) | |
| .ToList(); | |
| var identities = new List<ApplicationUserAssignedIdentity>(); | |
| foreach (DictionaryEntry entry in this.ApplicationManagedIdentity) | |
| { | |
| var name = entry.Key?.ToString(); | |
| var principalId = entry.Value?.ToString(); | |
| if (string.IsNullOrWhiteSpace(name) || string.IsNullOrWhiteSpace(principalId)) | |
| { | |
| throw new PSArgumentException("ApplicationManagedIdentity must be a hashtable with non-empty string keys (identity names) and non-empty string values (principal identifiers)."); | |
| } | |
| identities.Add(new ApplicationUserAssignedIdentity( | |
| name: name, | |
| principalId: principalId)); | |
| } | |
| return identities; |
| } | ||
|
|
||
| currentApp.Identity.UserAssignedIdentities = this.UserAssignedIdentityId | ||
| ?.ToDictionary(id => id, id => new UserAssignedIdentity()); |
There was a problem hiding this comment.
When -UserAssignedIdentityId is bound, the cmdlet sets currentApp.Identity.UserAssignedIdentities but does not ensure currentApp.Identity.Type includes UserAssigned (and Identity may be newly created with Type == null). This can produce an invalid identity payload. Consider setting Identity.Type automatically when user-assigned IDs are provided (or enforcing that -IdentityType must be supplied alongside -UserAssignedIdentityId).
| ?.ToDictionary(id => id, id => new UserAssignedIdentity()); | |
| ?.ToDictionary(id => id, id => new UserAssignedIdentity()); | |
| // Ensure identity type includes UserAssigned when user-assigned identities are provided, | |
| // unless the caller explicitly specified -IdentityType. | |
| if (!this.IsParameterBound(c => c.IdentityType)) | |
| { | |
| var currentType = currentApp.Identity.Type; | |
| if (currentType == null || currentType == ManagedIdentityType.None) | |
| { | |
| currentApp.Identity.Type = ManagedIdentityType.UserAssigned; | |
| } | |
| else if (currentType == ManagedIdentityType.SystemAssigned) | |
| { | |
| currentApp.Identity.Type = ManagedIdentityType.SystemAssignedUserAssigned; | |
| } | |
| } |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = ByResourceId, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | ||
| [Parameter(Mandatory = false, ParameterSetName = ByInputObject, | ||
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] |
There was a problem hiding this comment.
The IdentityType help text lists SystemAssigned,UserAssigned, but the enum value users can pass is SystemAssignedUserAssigned (the comma form is only the serialized value). Update the help message to reflect the actual accepted PowerShell value(s) to avoid binding errors.
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | |
| [Parameter(Mandatory = false, ParameterSetName = ByResourceId, | |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | |
| [Parameter(Mandatory = false, ParameterSetName = ByInputObject, | |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned.")] | |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssignedUserAssigned.")] | |
| [Parameter(Mandatory = false, ParameterSetName = ByResourceId, | |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssignedUserAssigned.")] | |
| [Parameter(Mandatory = false, ParameterSetName = ByInputObject, | |
| HelpMessage = "Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssignedUserAssigned.")] |
| currentApp.ManagedIdentities = this.ApplicationManagedIdentity?.Cast<DictionaryEntry>() | ||
| .Select(entry => new ApplicationUserAssignedIdentity( | ||
| name: entry.Key as string, | ||
| principalId: entry.Value as string)) | ||
| .ToList(); |
There was a problem hiding this comment.
ApplicationManagedIdentity entries are cast with entry.Key as string / entry.Value as string. Non-string keys/values will become null and will trigger ApplicationUserAssignedIdentity.Validate() failures (Name/PrincipalId cannot be null). Add validation/conversion to ensure all hashtable keys/values are non-empty strings before constructing ApplicationUserAssignedIdentity objects.
| currentApp.ManagedIdentities = this.ApplicationManagedIdentity?.Cast<DictionaryEntry>() | |
| .Select(entry => new ApplicationUserAssignedIdentity( | |
| name: entry.Key as string, | |
| principalId: entry.Value as string)) | |
| .ToList(); | |
| if (this.ApplicationManagedIdentity != null) | |
| { | |
| var managedIdentities = new List<ApplicationUserAssignedIdentity>(); | |
| foreach (DictionaryEntry entry in this.ApplicationManagedIdentity) | |
| { | |
| if (entry.Key == null || entry.Value == null) | |
| { | |
| continue; | |
| } | |
| var nameString = entry.Key as string ?? entry.Key.ToString(); | |
| var principalIdString = entry.Value as string ?? entry.Value.ToString(); | |
| if (string.IsNullOrWhiteSpace(nameString) || string.IsNullOrWhiteSpace(principalIdString)) | |
| { | |
| continue; | |
| } | |
| managedIdentities.Add(new ApplicationUserAssignedIdentity( | |
| name: nameString, | |
| principalId: principalIdString)); | |
| } | |
| currentApp.ManagedIdentities = managedIdentities; | |
| } | |
| else | |
| { | |
| currentApp.ManagedIdentities = null; | |
| } |
| ### -IdentityType | ||
| Specify the type of managed identity for the application. Options are None, SystemAssigned, UserAssigned, and SystemAssigned,UserAssigned. | ||
|
|
||
| ```yaml | ||
| Type: ManagedIdentityType |
There was a problem hiding this comment.
-IdentityType docs mention SystemAssigned,UserAssigned, but the actual PowerShell enum value name is SystemAssignedUserAssigned (comma form is the serialized value). Update the parameter description so users know what value to pass.
| * Updated SFMC to latest api general version "2026-02-01" | ||
| * Fixed `Set-AzServiceFabricManagedClusterApplication` to use correct resource completer for managed clusters instead of classic clusters. | ||
| * Added parameters `-IdentityType`, `-UserAssignedIdentityId`, and `-ApplicationManagedIdentity` to `New-AzServiceFabricManagedClusterApplication` to support managed identity configuration on applications. | ||
| * Added parameters `-IdentityType`, `-UserAssignedIdentityId`, and `-ApplicationManagedIdentity` to `Set-AzServiceFabricManagedClusterApplication` to support managed identity configuration on applications. | ||
| * Added parameters `-AzureActiveDirectoryClientApplication`, `-AzureActiveDirectoryClusterApplication`, `-AzureActiveDirectoryTenantId`, `-EnableHttpGatewayExclusiveAuthMode`, `-HttpGatewayTokenAuthConnectionPort`, `-MaxPercentUnhealthyApplication`, `-MaxPercentUnhealthyNode`, `-MaxUnusedVersionsToKeep`, `-AddonFeature`, `-DdosProtectionPlanId`, `-EnableIpv6`, `-EnableServicePublicIP`, `-PublicIPPrefixId`, `-PublicIPv6PrefixId`, `-SubnetId`, `-UseCustomVnet`, `-VMImage`, `-AllocatedOutboundPort`, `-EnableOutboundOnlyNodeType`, and `-SkipManagedNsgAssignment` to `New-AzServiceFabricManagedCluster`. | ||
| * Added parameters `-AzureActiveDirectoryClientApplication`, `-AzureActiveDirectoryClusterApplication`, `-AzureActiveDirectoryTenantId`, `-EnableHttpGatewayExclusiveAuthMode`, `-HttpGatewayTokenAuthConnectionPort`, `-MaxPercentUnhealthyApplication`, `-MaxPercentUnhealthyNode`, `-MaxUnusedVersionsToKeep`, `-AddonFeature`, `-DdosProtectionPlanId`, `-PublicIPPrefixId`, `-PublicIPv6PrefixId`, `-VMImage`, `-AllocatedOutboundPort`, `-EnableOutboundOnlyNodeType`, and `-SkipManagedNsgAssignment` to `Set-AzServiceFabricManagedCluster`. |
There was a problem hiding this comment.
ChangeLog entry uses the acronym "SFMC" without expansion and includes double quotes around the API version. Per repo ChangeLog guidelines, expand less-obvious acronyms on first use and avoid problematic special characters like unescaped quotes (consider writing the version without quotes).
| @@ -168,9 +194,43 @@ private ApplicationResource GetNewAppParameters(string location) | |||
| version: this.GetAppTypeArmResourceId(this.DefaultContext.Subscription.Id, this.ResourceGroupName, this.ClusterName, this.ApplicationTypeName, this.ApplicationTypeVersion), | |||
| parameters: this.ApplicationParameter?.Cast<DictionaryEntry>().ToDictionary(d => d.Key as string, d => d.Value as string), | |||
| location: location, | |||
| identity: this.GetManagedIdentity(), | |||
| managedIdentities: this.GetApplicationManagedIdentities(), | |||
| tags: this.Tag?.Cast<DictionaryEntry>().ToDictionary(d => d.Key as string, d => d.Value as string)); | |||
| } | |||
|
|
|||
| private ManagedIdentity GetManagedIdentity() | |||
| { | |||
| if (!this.IsParameterBound(c => c.IdentityType)) | |||
| { | |||
| return null; | |||
| } | |||
|
|
|||
| var identity = new ManagedIdentity(type: this.IdentityType); | |||
|
|
|||
| if (this.UserAssignedIdentityId != null && this.UserAssignedIdentityId.Length > 0) | |||
| { | |||
| identity.UserAssignedIdentities = this.UserAssignedIdentityId | |||
| .ToDictionary(id => id, id => new UserAssignedIdentity()); | |||
| } | |||
|
|
|||
| return identity; | |||
| } | |||
There was a problem hiding this comment.
UserAssignedIdentityId can be specified without IdentityType, but GetManagedIdentity() returns null unless IdentityType is bound, so user-assigned identities are silently ignored. Consider either making -IdentityType mandatory when -UserAssignedIdentityId is provided, or inferring/setting IdentityType to UserAssigned (or SystemAssignedUserAssigned) when user-assigned IDs are supplied.
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Description
Set-AzServiceFabricManagedClusterApplicationto use correct resource completer for managed clusters instead of classic clusters.-IdentityType,-UserAssignedIdentityId, and-ApplicationManagedIdentitytoNew-AzServiceFabricManagedClusterApplicationto support managed identity configuration on applications.-IdentityType,-UserAssignedIdentityId, and-ApplicationManagedIdentitytoSet-AzServiceFabricManagedClusterApplicationto support managed identity configuration on applications.-AzureActiveDirectoryClientApplication,-AzureActiveDirectoryClusterApplication,-AzureActiveDirectoryTenantId,-EnableHttpGatewayExclusiveAuthMode,-HttpGatewayTokenAuthConnectionPort,-MaxPercentUnhealthyApplications,-MaxPercentUnhealthyNodes,-MaxUnusedVersionsToKeep,-AddonFeature,-DdosProtectionPlanId,-EnableIpv6,-EnableServicePublicIP,-PublicIPPrefixId,-PublicIPv6PrefixId,-SubnetId,-UseCustomVnet,-VMImage,-AllocatedOutboundPort,-EnableOutboundOnlyNodeTypes, and-SkipManagedNsgAssignmenttoNew-AzServiceFabricManagedCluster.-AzureActiveDirectoryClientApplication,-AzureActiveDirectoryClusterApplication,-AzureActiveDirectoryTenantId,-EnableHttpGatewayExclusiveAuthMode,-HttpGatewayTokenAuthConnectionPort,-MaxPercentUnhealthyApplications,-MaxPercentUnhealthyNodes,-MaxUnusedVersionsToKeep,-AddonFeature,-DdosProtectionPlanId,-PublicIPPrefixId,-PublicIPv6PrefixId,-VMImage,-AllocatedOutboundPort,-EnableOutboundOnlyNodeTypes, and-SkipManagedNsgAssignmenttoSet-AzServiceFabricManagedCluster.Manualoption for the-UpgradeModeparameter inSet-AzServiceFabricManagedCluster.-IsOutboundOnly,-EnableResilientEphemeralOSDisk,-EnableAcceleratedNetworking,-EnableEncryptionAtHost,-EnableNodePublicIP,-EnableNodePublicIPv6,-SecureBootEnabled, and-UseEphemeralOSDisktoNew-AzServiceFabricManagedNodeType.-IsOutboundOnly,-EnableResilientEphemeralOSDisk,-EnableAcceleratedNetworking,-EnableEncryptionAtHost,-EnableNodePublicIP,-EnableNodePublicIPv6,-SecureBootEnabled, and-UseEphemeralOSDisktoSet-AzServiceFabricManagedNodeType.-ServiceDnsNametoNew-AzServiceFabricManagedClusterServicefor DNS-based service discovery.Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.