User accounts
Organise Microsoft Entra ID accounts around employees and roles, match permissions to business needs and plan reviews when people join, change responsibilities or leave the company so that access follows their situation.
Microsoft Entra ID
Microsoft Entra ID for SMEs: organise identities, MFA, external access and leavers, with clear rules matched to working practices and available licences.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

Microsoft Entra ID supports authentication and identity management for Microsoft cloud services and compatible applications. For an SME, the task is to establish a clear view of employee accounts, administrators, guests and identities used by applications.
An access review starts with their current purpose, rather than the number of accounts shown in a console. We can compare business roles with assigned permissions and identify exceptions needing clarification. This complements your business cybersecurity approach by assigning ownership to access decisions, including decisions about accounts that no longer have an obvious owner.
Organise Microsoft Entra ID accounts around employees and roles, match permissions to business needs and plan reviews when people join, change responsibilities or leave the company so that access follows their situation.
Review Microsoft Entra ID authentication methods and prepare users for MFA with a pilot, understandable guidance and a recovery procedure for situations where their usual methods become unavailable during normal business operations.
Assess Microsoft Entra ID Conditional Access policies against available licences and applications, test their effects on representative user profiles and document exceptions as well as the conditions for reversing a disruptive change.
Inventory guest accounts in Microsoft Entra ID, identify the owner of each collaboration and reassess permissions when an assignment changes or access to business resources is no longer justified by the work involved.
Distinguish privileged Microsoft Entra ID accounts from ordinary access, document the roles and authorised people and prepare controlled recovery access without distributing secrets in a list shared broadly across the organisation.
Identify identities used by applications in Microsoft Entra ID, confirm their purpose and permissions with a responsible owner, then include them in access reviews for the cloud environment that your business operates.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
A review of your environment, identification of vulnerabilities and a prioritised action plan.
Securing identities, MFA, permissions and workstations.
Workstations, email, Microsoft 365, networks and backups.
Workshops and training to build good everyday habits.
Alert monitoring and a prompt response to incidents.
Follow-up, optimisation and support from a dedicated contact.
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.
Roles, permissions and protections suited to the agreed scope.
Identified dependencies, with backup and recovery arrangements to prepare.
Documented joiners, leavers and changes in responsibility.
Accessible configuration, licence and upcoming renewal records.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Microsoft Entra security defaults provide a baseline for suitable environments. Conditional Access policies allow more detailed rules and require appropriate licences, including P1 or P2 depending on the capabilities used.
The project should check what is already enabled, which authentication methods people use and which applications could be affected. Prepare users and test a representative group before extending a rule. Exceptions should be justified, limited and reviewed rather than becoming permanent by default. Make sure the business understands the effect of a policy before approving it.
An account should follow the person's situation. For a new starter, a manager approves useful access; when a role changes, previous permissions need review; when someone leaves, data and access need coordinated handling.
The procedure should also cover external applications, devices and shared folders. Microsoft Intune may be involved for managed devices and applications. Removing access should not unintentionally remove information colleagues need or material the business must retain. Specify who approves the timing, who performs the technical steps and who verifies completion.
Administrative accounts need a separate inventory showing assigned roles and the people authorised to use them. Also plan how legitimate access can be restored if normal authentication methods become unavailable.
We can scope documentation of emergency access, sign-in checks and alert handling. Secrets should not be placed in an ordinary list shared with everyone. IT governance helps define change approvals and review frequency while keeping your business in control. Recovery arrangements should be tested under an agreed procedure, without disrupting normal access.
Not automatically. Microsoft distinguishes Entra ID, Active Directory Domain Services and Entra Domain Services. Local applications may depend on specific protocols or capabilities. Identify those dependencies before removing a directory, changing device sign-in or choosing a hybrid architecture. Similar naming does not mean the services can be substituted without assessment.
It is an important protection, but it does not correct excessive permissions, a compromised device or an application granted inappropriate access. Review authentication methods, privileged accounts, sharing and recovery procedures as well. Business approval is still needed to determine who should access information. Treat MFA as part of the control framework, rather than the whole framework.
Identify affected applications and user profiles, then prepare a pilot and a controlled recovery method. Schedule changes and check their effects before broad rollout. The engagement should specify who can decide to reverse a configuration and how users will be informed if essential access is disrupted. Keep the original settings and the reason for the change documented.
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