Read the catalog boundary
The Azure Service Catalog lists the Azure APIs represented in the product model. Its Azure checkmark means the service can remain on its native cloud. It does not mean that a cross-cloud service adapter is offered. Each linked service page states the same availability boundary. It intentionally omits backend choices, adapter commands, operation coverage, and service-adapter SLAs because no cross-cloud mapping is being offered for that origin API.When Azure is the target
This restriction applies to the API used by the application, not to Azure as a destination. An application using a supported AWS API can still select an offered Azure backend. Start from the Amazon Web Services Service Catalog, choose the AWS-origin service, and check its Azure target section. For example, an application that uses the Amazon S3 API can evaluate the offered S3-to-Blob Storage mapping. That does not imply the reverse Blob Storage-to-S3 direction.Plan against explicit directions
Treat every service mapping as directional. Do not infer an Azure-origin adapter from a similarly named AWS-origin mapping, a shared backend, or a provider logo. If your application uses an Azure API and must move to another cloud, contact Tensor9 with the origin service, intended target, and required operations.Browse Azure availability
See which origin services remain available on Azure only.
Browse offered AWS mappings
Find AWS-origin APIs with documented Azure backend choices.