On-Premise Service Fabric Deployment Target Fails to Connect

We have an on-premise service fabric cluster that is secured using Windows. Using PowerShell to connect looks like this: Connect-ServiceFabricCluster machine:19000 -WindowsCredential

Here is an example of what the SF cluster config would look like:

I only see options to connect unsecured, secured w/ client cert, or secured with Azure AD.

Is there anyway to support this cluster configuration when setting up a SF deployment target?


Hi Brian,

Thanks for getting in touch. When we added support for Service Fabric the focus was support for Azure, so the WindowsCredential mode wasn’t considered a priority. We have a UserVoice suggestion to add support for it, so please head over there and add your weight to the conversation to help us prioritize.

Sorry there isn’t a better answer at the moment.