Expertise
Microsoft Entra ID for organisations in Bern.
We support your Microsoft Entra ID project from Bern and Sachseln. We agree with your team how to organise workshops, delivery and collaboration in Bern. Our first conversation focuses on your existing environment and the task you need to solve.
People, guests, services, agents
A new employee gets her account on her first day, signs in with a passkey and sees exactly the applications of her role; her access ends with her last working day. The same rules apply to guests, service accounts and AI agents from Copilot Studio, Microsoft Foundry or your own applications. How we run Zero Trust as a project is described under Zero Trust & Identity Security.
Accounts, sign-in, roles
We set up accounts, sign-in, roles and policies with your IT, starting with the accounts that hold the most rights, and document every exception. The building blocks for people and agents:
- LifecycleAccounts from the HR system or on-premises AD, groups by role, access packages with an expiry date and regular reviews by managers.Result: joining, changing role and leaving adjust rights automatically.
- Passkeys and MFAPasskey profiles per group, device-bound passkeys for administrators, synced passkeys for everyone else, registration right at sign-in.Result: most sign-ins run without a password and withstand phishing.
- Conditional AccessPolicies by account, device, location and risk, first in report-only mode, then with a pilot group.Result: the sign-in log shows for every denied sign-in which policy applied.
- Administrator rightsSeparate admin accounts, roles through Privileged Identity Management only for a limited time and with a justification, emergency accounts with a FIDO2 key or certificate.Result: only the emergency accounts hold permanent admin rights.
- Agents with their own identityAgent ID for agents from Copilot Studio, Microsoft Foundry or other platforms, with a sponsor, a blueprint and dedicated policies for autonomous agents.Result: every agent has an accountable person, and your IT can block it with one policy.
- Guests and partnersB2B guests, access between the tenants of related companies and guest reviews per project.Result: partners work with their own account and lose access when the project ends.
Know your applications and lockout effects
We need an inventory of applications, directory connections, service and emergency accounts and the groups with critical rights. We clarify licences per building block: Conditional Access needs at least Entra ID P1, policies for agents also need Agent 365 or Microsoft 365 E7. Existing sign-in methods and the effects of a lockout are clarified before any change.
Sign-ins under test
We test permitted and denied sign-ins, role changes, guest access and employee departures, and for agents also a sign-in with elevated risk. The emergency accounts sign in during the test. Logs and documented exceptions help your operations team maintain policies and investigate problems.
Arrange collaboration around the project
Our offices are in Bern and Sachseln. Remote work and on-site meetings are arranged according to project needs. We clarify participants, working language, access and any travel effort beforehand. The location describes the service area, not an additional CNEXT office.
Sound familiar? Tell us where you stand today.
Contact in BernRelated to your task
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.