Deploying an Azure function that requires access to an Azure resource requires some "identity" stuff. I'll show you how.

Managed service fabric simplifies a bunch of stuff over its predecessor. But still, there are times when you need to get out to your machines to see what's what. In other words, there are times when you just have to get under the hood.

Using reliable collections is scary if you're used to working with a database. Establishing a backup and restore procedure reduces some of that anxiety.

Set up a DevOps pipeline to deploy code changes to the cluster. This is a basic pipeline in that the entire SF app goes out with no regard for versioning or surgical precision with respect to adjusting only one or two services leaving the others alone. This is a big old "replace everything" pipeline.

Having a brand new shiny managed service fabric cluster, I now need to put some security behind an exposed API endpoint with which my client apps need to connect.

A tale of woe and bad documentation getting my shiny new Managed Service Cluster up and running.