Microsoft

What we manage inside Microsoft 365 and Azure

Inside Microsoft 365 we configure the tools your business relies on daily: Exchange Online for email, SharePoint Online and OneDrive for shared files, Teams for chat and video calls. Entra ID handles user accounts, groups and permissions centrally, while Intune lets us apply security policies to company devices, including the ones your team uses on the road. On Azure we build virtual machines, storage and backup for workloads that do not stay on premises, using Azure Hybrid Benefit to reuse Windows Server licences your business already owns.

We do not stop at activating licences. We configure the tenant around how your business actually works: departments, sites, different permission levels for staff handling sensitive data and everyone else. When a hybrid setup is needed we connect Microsoft 365 to your local Active Directory with Entra Connect, so credentials stay the same across the on premises domain and the cloud. We also set external sharing rules for files, so company documents do not end up accessible to anyone with a link.

• Exchange Online, SharePoint, OneDrive and Teams
• Entra ID for identity and permissions
• Intune for device management
• Virtual machines and storage on Azure

When it makes sense and when to stay on premises

Microsoft 365 is the right choice for businesses that need reliable email, files shared across multiple sites and collaboration tools without maintaining dedicated servers in the office. It is especially useful for teams that work off site or remotely, since access to data does not depend on a single physical workstation in the building. The same applies to growing businesses that do not want to size local hardware for every new hire.

It is not always the best fit. Some businesses run management software tied to an on premises Windows Server domain, or have regulatory requirements that keep certain data on physical servers in house. In these cases we build a hybrid setup, with Microsoft 365 for email and collaboration and Windows Server for legacy applications, or we recommend staying on premises if moving to the cloud brings no real benefit. We assess the scenario before proposing a migration, not after.

How we work: analysis, migration and testing

Before touching a single mailbox we review the existing infrastructure: where the data lives today, which applications depend on email or files, how many users need to move. Based on that we choose the right migration method, cutover for a handful of users, staged or IMAP for larger volumes, and plan a window that keeps disruption to a minimum for people who rely on email every working day.

After the migration we verify every mailbox, calendar and contact arrived intact before calling the project done. We train users on the features they will actually use, not on the entire Microsoft 365 suite. Ongoing tenant management, from licences to security updates, stays with our Melzo lab, with the same contact who ran the migration, not an anonymous help desk that changes every time you call.

Security, backup and licence management

We set up multi-factor authentication on every account, with conditional access policies that block suspicious sign-ins from unrecognised countries or devices. Backup of Microsoft 365 data is not included by default under Microsoft's responsibility: the platform guarantees service availability, not the recovery of an email or file deleted by mistake weeks earlier. That is why we always pair Microsoft 365 with an independent backup, run with third party tools and kept separate from the tenant itself.

We periodically review the licence plans in use, because it is common to find businesses paying for higher tiers than they need or keeping accounts active for people who left months ago. We support clients who need to comply with the NIS2 directive by configuring access controls and monitoring in line with the required obligations.