Exchange Online
Organise email, calendars and shared mailboxes in Exchange Online, with delegation rules, migration preparation and checks suited to the addresses your business uses, including those needed by existing applications and devices.
Microsoft 365
Sunitech supports your adoption of Microsoft 365 with a practical, local approach. Email, collaboration, files, security and support: a complete environment to help your business grow.
Microsoft 365 tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

An SME can already have Microsoft 365 while still dealing with scattered files, forgotten accounts and conversations that are difficult to find. The first task is to connect the tools with specific needs: replying to customers, preparing a case file, working from another site or handing over an assignment.
Our Cloud and Microsoft 365 service can begin with this review. Together, we identify the people involved, essential applications and observed problems before proposing a defined scope for change.
Organise email, calendars and shared mailboxes in Exchange Online, with delegation rules, migration preparation and checks suited to the addresses your business uses, including those needed by existing applications and devices.
Structure Microsoft Teams conversations, meetings and channels around teams and projects, defining owners, authorised guests and the locations where useful shared documents should remain available throughout the work and after project closure.
Create shared document spaces in SharePoint, with understandable libraries, permissions assigned to groups and identified owners so that working files remain accessible when employees change roles or leave your organisation.
Prepare individual working files in OneDrive for Business, then explain synchronisation, offline availability and the move to SharePoint when a document becomes a reference that needs to be managed by a team.
Manage devices and applications with Microsoft Intune according to their platforms and licences, preparing profiles suited to employee roles, a gradual rollout and a support procedure for devices that fail compliance checks.
Organise identities and access in Microsoft Entra ID, review authentication methods and document employee arrivals, role changes and departures, with identified owners responsible for each decision about permissions to business information.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Prepare data, accounts and cutover stages, with testing and a rollback plan.
Configure tools and integrate them into your environment within the agreed scope.
Define permissions, available protections and useful checks.
Clarify workspaces, responsibilities, sharing rules and team practices.
Check data protection needs and prepare recovery procedures.
Support adoption and agree ongoing assistance suited to your employees.
We start with your teams’ needs, business applications and organisational constraints.

Share client files between colleagues, with appropriate access and documents that are easy to find.

Protect patient records and maintain the tools needed for consultations.

Find plans and files on site while keeping control of access for everyone involved.

Organise access for employees, elected representatives and volunteers, and make handovers easier when teams change.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Multi-factor authentication, phishing protection and access management.
Clear folder structures, access permissions and document lifecycles.
Ongoing management of joiners, leavers, licences and roles.
Retention, auditing and checks defined around your requirements and licences.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Selecting a plan means considering installed and browser-based applications, email, mobile working and the security capabilities you need. Teams availability, add-ons and commercial terms must be checked against the subscription you actually purchase.
Microsoft's business overview provides the general framework. We then recommend a simple matrix covering each employee profile, its tasks, the required licence and the person responsible for assignment. This helps with starters, leavers and reviews of unused subscriptions.
Before moving data, list the mailboxes, folders, permissions and applications that depend on the current environment. A pilot lets you test accounts, incoming messages and representative documents.
The schedule should include communication with staff, checks after transfer and an agreed response if something differs from expectations. For shared documents, define the SharePoint structure before copying files. Reproducing an old folder structure without reviewing its permissions can carry the same problems into the new system. Decide who will approve each stage and retain the information needed to investigate missing or inaccessible content.
Microsoft 365 still needs administration. User permissions, privileged accounts, external access and recovery arrangements need named owners. Available settings depend on the services and licences selected.
Identity management uses Microsoft Entra ID. We can scope an access review, a starter and leaver procedure, and recurring checks. The engagement defines deliverables and each party's responsibilities; buying a subscription does not, by itself, define the support service. Record decisions so that a change of administrator does not leave your organisation dependent on someone's memory.
Not necessarily. Someone working mainly in a browser may have different needs from a colleague who depends on installed applications. However, check each plan's entitlements, required security capabilities and assignment conditions. A cheaper licence brings little benefit if it prevents an essential task. Document the reason for each profile rather than allocating subscriptions by habit.
Yes, a limited scope can be assessed: one team, a document collection or email. Plan for coexistence with retained tools, possible duplicate work and the location of authoritative documents. An IT audit helps clarify dependencies before deciding which changes should happen first. A pilot should have clear acceptance criteria and a decision point.
Cloud service availability and your business's ability to recover a document or resume work need separate consideration. Define the data to retain, deletion scenarios, expected recovery times and restoration tests. Assess built-in capabilities and any additional solutions against those requirements, including who will carry out recovery and confirm that the restored information is usable.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us