Get started — Documentation — FinOps Move2Cloud

Signing up and signing in

Your Move2Cloud account lets you sign in to FinOps with your e-mail address, Google or Microsoft. Two-step sign-in protects access. A person can belong to several organisations and keeps their role in each.

“Register”, below the sign-in page: your e-mail address, first name and last name, or your Google or Microsoft account.

The sign-in page of your Move2Cloud account: e-mail address and password, or Google or Microsoft account.

Each new organisation has a free 14-day trial, without a bank card. The Plans page describes the offers, their limits and what happens when a trial ends.

The private “Signing up and signing in” guide in the console documentation explains account creation, address verification, choosing an organisation and sign-in settings.

Providers and the access they need

Each cloud account is connected with an access that you create and keep the control of, read-only wherever the provider allows it (Scalingo has no read-only token; the tool only reads with it): removing it cuts the access at once.

Cloud accounts → Accounts: the providers selected, the accounts connected against the plan, then one tab per provider with its accounts and “Add an account”.

Sovereign providers

OVHcloudA token limited to reading Public Cloud projects (GET /cloud/project and its sub-paths).
ScalingoAn API token. Scalingo does not offer a read-only token; the tool only reads.
ScalewayAn API key of an IAM application that only has the BillingReadOnly and ProjectReadOnly permission sets.

American providers

AWSA read-only role created by a ready-to-launch CloudFormation stack (costs, and optionally the inventory and AWS's recommendations), with no key to hand to us. Failing that, an IAM user limited to ce:GetCostAndUsage and ce:GetCostForecast.
AzureThe FinOps Move2Cloud application, which you authorise in your Microsoft Entra ID directory, then to which you give the Cost Management Reader role on a management group or on the subscriptions to track, with no secret to hand to us. Failing that, your own application with a client secret. No Contributor or Owner role is needed. Depending on your Azure contract, access to costs may also depend on billing permissions.
Google CloudA service account with the BigQuery Data Viewer role on the billing export's dataset and the BigQuery Job User role on its project. The tool only runs read queries on that export.

The step-by-step procedure of each provider, with screenshots, is in “Connecting a provider”, in the documentation of the console.

What is followed for each provider

What the tool reads at each provider, where its figures come from and what it draws from them. The tags set on resources are read at no provider: a project's environment (production or non-production) is deduced from its name, and can be corrected by hand.

	OVHcloud	Scalingo	Scaleway	AWS	Azure	Google Cloud
What is followed	Each Public Cloud project	Each app, region by region	Each project of the organisation	Each AWS account (the whole organisation from the management account)	Each subscription	Each project, and what belongs to none (“Outside projects”)
Source of the costs	Usage API of the Public Cloud projects	Invoices for closed months; an estimate for the current month	Billing API (consumptions)	Cost Explorer, usage cost (UnblendedCost)	Cost Management, actual cost (ActualCost)	Billing export to BigQuery
Current month	Usage recorded by OVHcloud	Estimated: running containers and add-ons, at list price, since the start of the month	Usage recorded by Scaleway	AWS costs up to and including today	Azure costs up to today	What the export holds
Credits, discounts, taxes	OVHcloud's amounts excluding tax	Closed months: the gap between the invoice and its detail (credits, discounts) on a “Discounts and adjustments” line	Scaleway's amounts excluding tax	Taxes, credits and refunds left out	Actual cost excluding tax, your contract's discounts applied	Credits deducted (free tier, commitment discounts); taxes left out
Currency	Euros	Euros	Euros; dollars converted	Dollars converted to euros	Billing currency; dollars converted	Billing currency; dollars converted
History	Up to 6 months (OVHcloud's limit)	12 months of invoices	12 months	12 months	12 months (Azure's one-year limit)	12 months, since the export was turned on
End-of-month forecast	OVHcloud's	Computed at the price of what runs, to the end of the month	At the month's pace	AWS's; failing that, at the month's pace	Azure's; failing that, at the month's pace	At the month's pace
Recommendations	Non-production left on; instances stopped but billed; permanent instances billed by the hour (commitment); Kubernetes pools without autoscaling or headroom; unattached volumes; old snapshots	Non-production left on; oversized containers; paid add-ons on a stopped app	Non-production left on	AWS's advice (Cost Optimization Hub): oversized or unused resources, cheaper generation, commitments; non-production left on; oversized ECS containers; commitment estimate	Non-production left on	Non-production left on
Also measured	Instances, volumes, snapshots, Kubernetes clusters (OVHcloud gives no processor or memory use)	Apps, containers, add-ons; memory and processor over 72 h, peaks kept 30 days	Instances, with the InstancesReadOnly permission	ECS services, processor and memory over 14 days	Detail by billing meter	Detail by SKU

“At the month's pace”: the month's spend to date, extended to the end of the month at the same pace. In the first days of a month, it is a rough guide.