The questions brokers ask most often about Cloudmore 5.0. If yours is not here, your account manager or the platform team can answer it.
Do we have to move to 5.0, and when?
Yes, eventually. No, not on our schedule.
Both interfaces run side by side from October until the end of January. You pick your switch date within that window and tell us when you are ready. The last switch date is 31 January 2027, and from February everyone is on 5.0.
Nothing happens without your go ahead. For the full timeline, see Switching over your Broker tenant.
Will our team or our customers need new logins?
No. Nobody needs a new account.
Existing usernames, passwords, MFA setups, SSO configurations and API credentials all continue to work. There is nothing to re-enrol.
The authentication system underneath is completely new, which is what makes passkeys and app-based MFA possible. Those are options you can adopt when it suits you, not requirements, and there is no deadline attached to them.
Is the beta a sandbox, or is it our live data?
It is your live data. This is the single most important thing to understand before you start.
Both interfaces share the same data layer. Anything you do in 5.0 is real, and it appears in the classic interface immediately. The same is true in reverse.
That is deliberate. It is the real platform with a new front, which is what makes it safe to use for real work rather than a throwaway practice environment. Treat it exactly as you treat the platform today. See New platform setup checklist.
Can we try it with a few people first?
Yes, and we recommend it.
The beta is reached through a separate URL. Share it with whoever you choose. Everyone else carries on in the current interface exactly as they do today, until you decide to widen access.
There is no all-or-nothing moment until you ask for your switch.
Will our API integrations keep working?
Yes. The API is not affected by 5.0. Every endpoint and call you use today continues to work exactly as it does now.
Separately, we released a new set of billing API endpoints. They are faster, because the data is pre-generated, and they offer more endpoints, filters and properties. These are additions, not replacements. Your existing integrations keep working, though we do encourage you to move across when convenient.
Will our branding carry over?
Yes. Your main brand colours are migrated, so nothing looks wrong on day one. Your branded URL stays the same, with no DNS or address changes on your side.
There is also considerably more you can control than before, including the header banner style, separate highlight and button colours, gradients, the side menu and the page background.
It is worth reviewing early rather than accepting the migrated defaults. See step 3 of the New platform setup checklist.
Does the platform still perform well with thousands of organizations?
Yes. The improvement has been tested with very large data sets, and pagination keeps it fast whether you manage twenty customers or twenty thousand.
The gain applies across the platform rather than to a handful of pages, including the general billing report. For the benchmark figures, see What has changed.
What happens to the previous general billing report?
It is being retired. The current general billing report replaces it, with the drill-down navigation, scheduling and export history described on the what has changed page.
If anyone on your team still relies on the previous report, move them across during the beta window rather than waiting. Access ends when your tenant switches.
Will our own documentation and screenshots be out of date?
Yes, for anything that shows the interface. The functions are broadly the same, but menus, labels and page layouts have changed.
The beta window exists partly for this. Use it to refresh manuals, screenshots and any local-language guides you maintain for your staff or your customers.
We will provide an updated knowledge base you can reuse, along with brandable announcement templates and short guides you can adapt, so you are not starting from a blank page. See step 7 of the New platform setup checklist.
Can a customer with several Microsoft tenants be managed as one organization?
No. This is unchanged in 5.0.
An organization maps to a single Microsoft tenant. A customer with several tenants is still managed as several organizations, one per tenant.
If you operate several brokers as a group, that is a different case and it is covered below.
We operate several brokers. Can we see them all in one place?
Yes, and this improved in Q3.
A seller account can now step straight into any linked broker. One login, one group view, and switching between brokers is instant with no signing out and back in.
Seller-level billing also aggregates across your brokers, including Microsoft services, so you get a combined view of cost and sales rather than opening each broker separately.
Can we track Azure reservation expiry across our customer base?
Not yet. This is not part of 5.0 and it is not in the current Q4 plan.
We know it is wanted and it is on our radar. If it matters to you, tell your account manager, because what we hear from you shapes what gets built next.
Still have a question?
Your account manager is the fastest route for anything about your rollout window or the beta invitation.
For questions about the platform itself, or help with any step, email the platform team at platformsupport@cloudmore.com.