When applying changes to TAS using Azure storage, Cloud Controller might fail to start due to an error when accessing the blobstore.
In /var/vcap/sys/log/cloud_controller_ng/cloud_controller_ng.log you see an AuthorizationFailure (403) error message:
{"timestamp":"<REDACTED>","message":"Error with blobstore: Fog::AzureRM::CustomAzureCoreHttpError - AuthorizationFailure (403): This request is not authorized to perform this operation.\nRequestId:<REDACTED>\nTime:<REDACTED>","log_level":"error","source":"cc.error_handling_client","data":{},"thread_id":<REDACTED>,"fiber_id":<REDACTED>,"process_id":<REDACTED>,"file":"/var/vcap/data/packages/cloud_controller_ng/<REDACTED>/cloud_controller_ng/lib/cloud_controller/blobstore/fog/error_handling_client.rb","lineno":67,"method":"rescue in error_handling"}
This error can be misleading since a 403 error code suggests a problem with your credentials, but it can also be caused by a network access issue.
Configuring file storage for TAS for VMs: https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/6-0/tpcf/pas-file-storage.html
Configure network access to Azure Storage: https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal#configure-network-access-to-azure-storage