Skip to main content

Cloud and Microsoft 365

Microsoft 365 and cloud services set up around your teams

Plan a clear move to Microsoft 365 and the cloud, or tidy what you already have, so email, files and collaboration work consistently across your offices.

  • Monday–Friday, 09:00–⁠18:00 CET/CEST
Corridor of server racks with beams of light rising toward a cloud in a pale blue sky

What you get

  • Microsoft 365 setup, licensing review and tenant organisation

  • Email, file and Teams migration planning

  • User, device and access configuration

  • Guidance on cloud storage, sharing and governance

Updated 11 Nov 2026

Microsoft 365 is the main workspace for many small and midsize companies: email, calendars, documents, chat and video meetings all live in the same place. That convenience also means that a poorly organised setup quickly becomes a problem, with duplicated licences, files scattered across personal drives and permissions nobody remembers granting. Our Microsoft 365 and cloud service helps you plan a clean move or tidy an existing environment, for teams in Europe, with support in English and Spanish.

Why setup matters more than the licence you choose

Buying Microsoft 365 is straightforward. Making it work for several offices is not. Decisions made in the first weeks, such as how users are named, how groups and shared mailboxes are structured, where documents are stored and who may share them externally, tend to stay in place for a long time because changing them later disrupts real work.

Companies operating in more than one country also deal with different languages, time zones, local suppliers and, in some cases, different expectations about where data is held. We do not provide legal advice, but we can document how your environment is configured so that your legal adviser or customers can understand it. The goal is a setup that is simple to explain, simple to administer and consistent from one office to the next.

What’s included in our Microsoft 365 and cloud service

Assessment and licensing review

We start by looking at what you already use: existing subscriptions, mailboxes, file servers, third-party tools and any other cloud services. We then compare it with how your teams actually work, so licences match roles instead of being bought in one size for everyone. This often reveals unused subscriptions and overlapping tools that can be retired. To compare the Business Basic, Standard and Premium plans, see our guide to Microsoft 365 Business plans.

Tenant organisation and identity

A well-organised tenant begins with identity. We help define naming conventions, user and group structure, administrator roles, and sign-in rules including multi-factor authentication. Where the business already has an on-premises directory, we explain the options for connecting it. These choices also support the security work described under cybersecurity. Our Microsoft 365 security baseline checklist lists the basic settings worth reviewing.

Email, files and collaboration migration

We plan the move from existing email, file servers or other collaboration platforms into Exchange Online, SharePoint, OneDrive and Teams. Planning covers what to migrate and what to archive, the order in which teams move, how to keep email flowing during the transition, and how to communicate changes so users are not surprised. Cut-over dates are agreed with you around your calendar and peaks of activity. If you are moving from Google Workspace, our migration guide covers the plan, cutover and post-move checks.

Devices and user setup

We help configure laptops, phones and tablets so they sign in with company accounts, receive updates and follow the policies you have agreed. Onboarding and offboarding steps are written down so that new colleagues receive the right access and leavers lose it promptly.

Sharing, storage and governance

Collaboration works best with clear rules: which team owns which library, how guests are invited, how long files are retained and what may be shared outside the company. We help you set sensible defaults and document them in plain language. We also discuss backup of cloud data, because a cloud provider’s availability is not the same as a recoverable copy of your information.

Microsoft 365 backup

A cloud provider’s availability is not the same as a recoverable copy of your information. We discuss backup of cloud data when setting up sharing, storage and governance for your Microsoft 365 environment.

Microsoft runs the platform, and you remain responsible for your own data. This is usually called the shared responsibility model: the service is built to stay available, while deciding who can delete information, how long it is kept and how it is recovered after a mistake or an attack is up to the customer. Check Microsoft’s current documentation for how this applies to your plan.

Built-in features such as recycle bins, version history and retention settings help with accidental deletion, but retention is not backup. Those windows are limited, they depend on your plan and configuration, and they can change, so check the current Microsoft documentation instead of assuming a period. A malicious deletion, an error synchronised to every device or a compromised account can also reach those copies.

When you talk to any provider about backup of Microsoft 365 data, it is worth asking:

  • Which data is covered (mailboxes, files, Teams, SharePoint sites), and which is not?
  • Who can delete or change the copies, and are they kept apart from everyday administrator accounts?
  • How long are copies kept, and is that agreed in writing?
  • When was a restore last tested, and what was the result?

We discuss these points as part of setup, and scope is agreed per organisation. For the wider approach to copies, recovery targets and restore tests, read our backup and recovery guide. Many of the account settings that protect your data are listed in our Microsoft 365 security baseline checklist.

How a Microsoft 365 or cloud project starts

Before anyone proposes a design, we read what already exists. Four pieces of work come first, and each narrows the questions left for the next.

Licence inventory

We list subscriptions, mailboxes, file servers and third-party tools, and set them against what each role actually uses. It comes first because a licence is paid for whether or not anyone opens the application. Typical findings are accounts of people who have left, one person holding two overlapping licences, and separate tools bought for something an existing plan may already cover. Check the current Microsoft documentation for what each plan includes before drawing conclusions.

Reading the current tenant

If a tenant exists, we review its users, groups, administrator roles and access rules before proposing changes. Useful questions: who holds administrator roles and still needs them, which external guests were never removed, which groups nobody can explain. A typical pitfall is a tenant created by one colleague or a former supplier, with nobody sure who owns it. If the current arrangement cannot be explained in plain language, it is usually easier to define the target structure and move towards it than to tidy in place.

Data-source map

We map the mailboxes, shared folders and source platforms that hold your data, which is what lets us decide what to migrate and what to archive. Moving data is the straightforward part; the decision that saves effort is what not to move, such as shared folders with no owner or mailboxes of leavers kept just in case. Whether information must be kept for legal or contractual reasons is a question for your legal adviser, and we note the answer before deciding what to archive.

Real usage per team

We talk to each team about how it actually collaborates, so that licences and the structure of sites and groups follow real work. Illustrative example, not a client: a team that says it only uses email may in practice run its week from a shared mailbox and a spreadsheet on a file server, and the new structure has to start from that, not from job titles. To decide what stays on a local server and what moves, see our on-site, cloud or hybrid server guide.

What the migration plan contains

The migration plan turns those readings into a sequence and answers four questions that would otherwise surface in the middle of the move. See a sample migration plan outline (illustrative example).

What migrates and what is archived

Material still needed for daily work moves. Material needed only for reference is archived where it can be found. Material with no owner and no evident purpose is raised with the people who may know before anything is dropped.

The order in which teams move

The order follows dependencies and your calendar, not seniority: teams that share a mailbox or a library usually move together, and a team with a deadline or a seasonal peak should not move just before it.

Mail continuity

The plan states how mail keeps arriving while some people are on the old system and others on the new. Usual pitfalls are forgotten shared mailboxes and aliases, forgotten forwarding rules, and devices, scanners or applications still pointing at the old server. Sender records for the domain are covered in SPF, DKIM and DMARC for your domain.

Communication to users

People need to know what changes for them, on which day, what they have to do themselves and where to ask for help. For wider planning questions, see our guide to planning IT and cloud services.

Ongoing work after go-live

If you want continuing work after the move, it falls into four areas, agreed per organisation and carried out within our published hours, Monday to Friday, 09:00–⁠18:00 CET/CEST.

Users and licences

Joiners, leavers and licence changes by role. Access follows the role: a new colleague receives what the role needs, and a leaver loses access, which also frees the licence. Our IT onboarding and offboarding checklist lists the steps worth agreeing.

Device management

Access policies, updates and device compliance, handled from a central console. The criterion is what a device must meet before it reaches company data, such as current updates and central management.

Permission reviews

A periodic review of administrators, external guests and sharing permissions. Permissions only grow unless someone looks: people change roles, projects end and shared links stay open.

Microsoft 365 backup review

We check the scope of the copy, who can delete it and the result of the last restore test; the reasoning is in the Microsoft 365 backup section above.

What this service does not cover

We do not give legal advice on data residency. Where data may be held, and whether an arrangement satisfies a contract or a regulation, is for your legal adviser. We can describe the configuration: which services are in use, what a plan offers (checked against Microsoft’s current documentation) and how the tenant is set up.

Who it’s for

This service is designed for organisations that want their cloud tools to be reliable and understandable without building a large internal IT team. Typical situations are:

  • A company moving from local servers or a different email platform to Microsoft 365.
  • A business that already uses Microsoft 365 but has inconsistent permissions, duplicated files or unmanaged devices.
  • A group of companies or offices merging separate tenants into a single, consistent environment.
  • A growing team that needs a repeatable way to add users, devices and shared spaces.
  • An organisation preparing for a wider security or support project and wanting solid foundations first.

Before we start

Scope, responsibilities and working arrangements are agreed for your organisation before work begins. We do not claim vendor status or special licensing terms; we help you make sound use of the platform and explain each choice in English or Spanish, whichever your team prefers.

For continuing administration and user support, see our managed IT services.

Once the environment is organised, the Automation and AI service can look at automating workflows across Microsoft 365 and your other tools.

To talk through your current setup or a planned move, contact us with a short summary of your users, offices and tools.

How we work

  1. Discovery

    We review your current systems, users, locations and priorities, and agree what is in scope.

  2. Design

    We propose a structure for identities, groups, storage and sharing, with the options and trade-offs explained.

  3. Preparation

    We prepare the tenant, test the configuration with a small group and plan communications for staff.

  4. Migration and go-live

    We move data and users in the agreed order, supporting your team through the changes.

  5. Handover and ongoing care

    We document how the environment is set up. If you want continuing administration and user support, it can be agreed as part of managed IT services.

FAQ

Questions, answered.

Can you plan our move to Microsoft 365?
Yes. We plan the move from your existing email, file servers or other collaboration platforms into Exchange Online, SharePoint, OneDrive and Teams, covering what to migrate and what to archive, the order in which teams move and how to keep email flowing during the transition. Cut-over dates are agreed with you around your calendar.
Does a cloud provider's availability replace a backup?
No. A cloud provider's availability is not the same as a recoverable copy of your information, so we discuss backup of cloud data as part of the sharing, storage and governance work.
Who sets sharing rules between countries?
Your organisation decides. We help you set sensible defaults, such as which team owns which library, how guests are invited, how long files are retained and what may be shared outside the company, and document them in plain language. We do not provide legal advice, but we can document how your environment is configured so that your legal adviser can understand it.
Does Microsoft back up our Microsoft 365 data?
Microsoft runs the platform and keeps the service available, but under the shared responsibility model you remain responsible for your own data: who can delete it, how long it is kept and how it is recovered after a mistake or an attack. Built-in protections exist, and what they cover depends on your plan and configuration. Check the current Microsoft documentation for what applies to you, and do not assume it replaces a separate, recoverable copy that you control.
Is the recycle bin or a retention setting the same as a backup?
No. Recycle bins, version history and retention settings help you undo accidental deletions, but they are not a backup. Their windows are limited, they depend on your plan and configuration, and they can change, so check the current Microsoft documentation instead of assuming a period. A malicious deletion, a synchronised error or a compromised account can also reach those copies, which is why a separate copy matters.
What should we ask a provider about Microsoft 365 backup?
Ask which data is covered (mailboxes, files, Teams, SharePoint sites) and which is not, who can delete or change the copies, whether they are kept apart from everyday administrator accounts, how long copies are kept and whether that is agreed in writing, and when a restore was last tested and what the result was. A clear, specific answer to each is a better sign than a general promise.
What can we do if someone deletes Microsoft 365 files or mail by mistake?
Act quickly, because built-in recovery windows are limited. Start with the recycle bin, version history or the recovery options for deleted items that Microsoft describes for your plan, and check the current Microsoft documentation for what is available and for how long. If that is no longer enough, only a separate copy can help, which is why it is worth knowing in advance what is backed up and testing a restore. Our backup and recovery guide covers how to plan and test this.
Can BlueNova IT help us review our Microsoft 365 backup?
We discuss backup of cloud data when setting up sharing, storage and governance, and we can help you work out what is covered today, what is not and which questions to put to a backup provider. Scope is agreed for each organisation before work begins. If you want to talk it through, use the contact form with a short summary of your users and tools.
What do you look at before designing a Microsoft 365 environment?
Four things: a licence inventory against real use by role, a read of the current tenant (users, groups, administrator roles and access rules), a map of data sources that decides what to migrate and what to archive, and how each team really uses the tools. The design follows from those readings.
What does the Microsoft 365 migration plan contain?
It states what migrates and what is archived, the order in which teams move, how mail keeps flowing while people are split between the old and new systems, and how users are told what changes for them, on which day and where to ask for help.
What ongoing Microsoft 365 work do you do after go-live?
Four areas: users and licences (joiners, leavers and changes by role), device management from a central console, periodic reviews of administrators, external guests and sharing permissions, and a review of the Microsoft 365 backup. They are carried out within our published hours, and scope is agreed per organisation.
Can you advise on where our Microsoft 365 data must be held?
No. We do not give legal advice on data residency; that is for your legal adviser. We can describe the configuration (services in use, options your plan offers, how the tenant is set up) so that your adviser has the facts.

Let’s talk about your IT.

Tell us what your team needs today and what you would like to improve.