> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart: Azure to Scaleway

> Check Azure-origin compatibility before selecting Scaleway as a target.

Cloud Adapter support is defined by a directed service profile, not by the fact that both clouds offer similar products. The Azure service catalog does not list a Scaleway target. Use a cataloged Azure route, or use the AWS-origin S3 route when your application can speak S3.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-quickstart-azure-to-scaleway-dark.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=c047d8488141e449350afbda2b326538" alt="An Azure to Scaleway route requires a directed service mapping before use." width="1100" height="360" data-path="images/diagrams/cloud-adapter-quickstart-azure-to-scaleway-dark.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-quickstart-azure-to-scaleway-light.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=ad506f59402fc61af0b1d3a5096fcb03" alt="An Azure to Scaleway route requires a directed service mapping before use." width="1100" height="360" data-path="images/diagrams/cloud-adapter-quickstart-azure-to-scaleway-light.svg" />
</Frame>

## Why a cloud pair is not enough

An application calls a specific Azure API with specific operations, fields, errors, identity behavior, and state semantics. A valid route must document how those behaviors map to a particular Scaleway service. Similar names such as blob storage and object storage do not establish that contract.

## Check the catalog

Start with the [Azure Service Catalog](/cloud-adapter/service-catalog/azure/catalog). Select the exact origin service and read across its target environments. A supported direction links to a detailed service page with:

* supported and rejected operations;
* capability and fidelity comparisons;
* identity and resource-name behavior;
* data, key, and state migration boundaries;
* target-specific limitations and other considerations.

If Scaleway is not present for the service, do not redirect the client endpoint and infer compatibility from a successful connection.

## Evaluate the application workload

Before choosing another route, capture the workload requirements:

1. Inventory every Azure service and operation the application calls.
2. Record request options, conditions, pagination, retries, and expected errors.
3. Create test data with no production dependencies.
4. Define the native Scaleway state you would verify after each operation.
5. Define cleanup for partial success and uncertain writes.
6. Keep origin credentials separate from any target verification credentials.

## What a supported route documents

| Evidence                 | Question answered                                                     |
| ------------------------ | --------------------------------------------------------------------- |
| Directed service profile | Which Azure behavior is adapted to which Scaleway service?            |
| Operation table          | Which calls can the application make?                                 |
| Capability comparison    | What changes at the target?                                           |
| Identity contract        | Which credential authenticates callers and which reaches Scaleway?    |
| Migration statement      | What existing data or state must be moved separately?                 |
| Lifecycle test           | Can create, read, update, expected failure, and delete be reproduced? |

Do not use a generic S3-compatibility test as evidence for an Azure Blob API route. It proves a different origin protocol.

For a runnable Scaleway example, use [AWS to Scaleway](/cloud-adapter/getting-started/aws-to-scaleway), whose S3 to Scaleway Object Storage profile is published. For an Azure-origin workflow, choose a supported target from the [Azure catalog](/cloud-adapter/service-catalog/azure/catalog).