Microsoft Entra ID and Active Directory consulting

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

What an identity review can clarify

  • Which accounts and roles carry the most risk
  • Which sign-in rules to pilot before wider rollout
  • Which applications still depend on Active Directory

Identity and access management services

We can start with one concern, such as privileged access or MFA, or review how your Microsoft identities work together.

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.

MFA and Conditional Access

Plan authentication methods and sign-in policies around users, devices and applications. Pilot changes, test exceptions and maintain emergency access.

Privileged Identity Management

Review standing administrative access. Where licensing and the role model allow, plan eligible roles, time limits, approvals and reviews using Microsoft Entra PIM.

Access roles and group ownership

Identify group owners and clarify how access is granted, reviewed and removed. Prioritise high-impact applications and shared resources.

Joiners, movers and leavers

Map account creation, role changes and offboarding. Check which steps can be automated, who approves exceptions and how to handle guests.

Active Directory modernisation

Review unused accounts, service dependencies and administrative boundaries. Plan changes in stages, with a way to test applications and recover if needed.

Entra ID, Active Directory or a hybrid setup?

The right setup depends on where your applications authenticate and who manages identities today.

Microsoft Entra ID

Suited to Microsoft 365 and cloud application sign-in. Review identity, device and application requirements before choosing policies.

Active Directory Domain Services

Identify legacy applications, service accounts and device processes that still depend on domain services. Use those dependencies to plan changes.

Hybrid identity

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.

What you get from an identity assessment

A clear view of access helps IT and application owners decide which changes to make first.

An inventory of higher-risk access

Review privileged roles, broad group memberships and accounts with unclear ownership.

A staged change plan

Identify pilot groups, exclusions, application checks and a recovery path before enforcing changes widely.

Review, pilot and roll out access changes

We agree the scope and the people responsible for approving changes before touching production policy.

Discuss your requirements
  1. Clarify the concern

    Identify affected users and systems, plus urgent issues and business constraints.

  2. Assess the current setup

    Review identity sources, roles, sign-in controls and application dependencies.

  3. Pilot and validate

    Test the proposed changes with representative users and applications. Check emergency access and agreed recovery steps.

  4. Hand over and review

    Document the policies, role model and operating responsibilities. Agree how to review access and handle exceptions.

Microsoft Entra ID and Active Directory FAQ

Answers on hybrid identity, licensing and administrative access.

Is Azure Active Directory the same as Microsoft Entra ID?

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.

Do we still need Active Directory with Microsoft 365?

That depends on local applications, device management, service accounts and other dependencies. We assess which workloads still need domain services before recommending a change.

Do we need Microsoft Entra ID P1 or P2?

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.

What does Privileged Identity Management do?

PIM can make selected administrative roles eligible for time-limited activation. Depending on the configuration, activation can require justification, approval or stronger authentication.

Can we start with an assessment only?

Yes. We can review the current environment and provide a prioritised plan you can use before making implementation decisions.

What affects the cost of an IAM project?

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.

Discuss your identity and access requirements

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

+49 911 25361972