Entra ID and hybrid identity
Map users, groups, sign-in and synchronisation dependencies. Assess which services still need Active Directory before changing where accounts are managed.
Find out who has access to what, and make it easier to manage that access. AURUM helps teams in Nuremberg and across Germany review Microsoft Entra ID, Active Directory and the way accounts are created, used and removed.
Microsoft Solutions Partner for Modern Work · Based in Nuremberg since 2014 · About AURUM
We can start with one concern, such as privileged access or MFA, or review how your Microsoft identities work together.
Map users, groups, sign-in and synchronisation dependencies. Assess which services still need Active Directory before changing where accounts are managed.
Plan authentication methods and sign-in policies around users, devices and applications. Pilot changes, test exceptions and maintain emergency access.
Review standing administrative access. Where licensing and the role model allow, plan eligible roles, time limits, approvals and reviews using Microsoft Entra PIM.
Identify group owners and clarify how access is granted, reviewed and removed. Prioritise high-impact applications and shared resources.
Map account creation, role changes and offboarding. Check which steps can be automated, who approves exceptions and how to handle guests.
Review unused accounts, service dependencies and administrative boundaries. Plan changes in stages, with a way to test applications and recover if needed.
The right setup depends on where your applications authenticate and who manages identities today.
Suited to Microsoft 365 and cloud application sign-in. Review identity, device and application requirements before choosing policies.
Identify legacy applications, service accounts and device processes that still depend on domain services. Use those dependencies to plan changes.
Connect identities across environments where required. Document which directory owns each record, how changes sync and what to do when synchronisation fails.
Conditional Access and privileged access features have different licence requirements. Check your plans against Microsoft’s Entra licensing reference.
A clear view of access helps IT and application owners decide which changes to make first.
Review privileged roles, broad group memberships and accounts with unclear ownership.
Identify pilot groups, exclusions, application checks and a recovery path before enforcing changes widely.
Assign owners for role reviews, exception handling and account lifecycle tasks. Connect the work to SharePoint permissions and governance where relevant.
We agree the scope and the people responsible for approving changes before touching production policy.
Discuss your requirementsIdentify affected users and systems, plus urgent issues and business constraints.
Review identity sources, roles, sign-in controls and application dependencies.
Test the proposed changes with representative users and applications. Check emergency access and agreed recovery steps.
Document the policies, role model and operating responsibilities. Agree how to review access and handle exceptions.
Answers on hybrid identity, licensing and administrative access.
Microsoft Entra ID is the current name for Azure Active Directory. Active Directory Domain Services is a separate directory service used by domain-joined devices and applications.
That depends on local applications, device management, service accounts and other dependencies. We assess which workloads still need domain services before recommending a change.
The answer depends on which features and users are in scope. Conditional Access generally requires P1 or an eligible bundle. Risk-based policies and PIM have additional licensing requirements, so we check the exact features against current Microsoft terms.
PIM can make selected administrative roles eligible for time-limited activation. Depending on the configuration, activation can require justification, approval or stronger authentication.
Yes. We can review the current environment and provide a prioritised plan you can use before making implementation decisions.
The initial consultation is free. Project cost depends on the number of directories and applications, policy complexity, testing and handover. Licence costs depend on the controls you choose.
Tell us which applications, roles or sign-in issues you want to review. We’ll help you identify a practical starting point in a free consultation in English.

Mustafa Yaylak
Managing Director, AURUM GmbH