Skip to Content
Jan 21, 2021 at 02:15 PM

Replacement for Open Service Broker Azure


Current SAP guidance for integration of Azure services on SAP Cloud Platform Cloud Foundry uses the "Open Service Broker for Azure". This project is no longer maintained by Microsoft, and is for that naturally considered "use at own risk". That project points towards "Azure Service Operator(for Kubernetes)", which is an implementation for Kubernetes and not Cloud Foundry.

Is there any new guidance on how to implement SCP CF <- Azure service integration? Or is it at least something on the roadmap for Embrace, that can mitigate the risk of running unmaintained software (as in OSBA), that doesn't involve implementing something yourself?