The MDC should pick up if the MSS is provisioned in a managed namespace in the cluster and, show it in the Mobile Services tab of a Mobile App inside MDC (i.e. available for binding).

A user should be able to bind their Mobile App to the MSS inside of MDC. This should result in the App being created inside the MSS Service.

When the binding is complete (App to MSS in MDC), the MSS config should be added to the mobile-services.json.

When the binding is complete, the route to the MSS UI console should be displayed, when the MSS Service is expanded under the Bound Services list in MDC.

When an unbinding is performed, MSS should be moved back to the unbound Services list in MDC and the App should not be visible in the MSS UI console.