Microsoft Entra ID

What is Entra ID?

Microsoft Entra ID (formerly Azure AD) is a cloud identity platform that centrally manages employee accounts (IDs) and ties together logins to Microsoft 365 and a wide range of cloud services. It is the foundation for controlling who can access which service, and it also serves as the starting point for SASE and Zero Trust.

Basics

The basics of Entra ID

As the number of cloud services grows, you end up managing separate IDs and passwords for each one, making it harder to balance convenience and security. Entra ID manages employee accounts in one place and makes logins safer and more convenient through the following capabilities.

  • Authentication (identity verification). The foundational function that confirms the person trying to log in is who they claim to be.
  • Single sign-on (SSO). A single login lets you use Microsoft 365 and multiple other services directly.
  • Multi-factor authentication (MFA). Combining a password with an approval on a smartphone, for example, to prevent impersonation.
  • Conditional access. Automatically controls whether access is allowed and whether additional authentication is required, based on location, device, and risk.

Because IDs, passwords, and access permissions are managed together in the cloud, services can be used securely under the same rules whether inside or outside the office.

Image

A visual overview

With a single login (SSO), users can securely access multiple authorized cloud services.

Employee Entra ID ID platform Microsoft 365 Allow App A Allow App B Allow Entra ID centralizes authentication; SSO reaches multiple services
Visual Guide

Understanding Entra ID with Diagrams

For those new to the jargon, three diagrams explain the ideas behind identity verification (MFA) and conditional access in Entra ID.

Diagram

An analogy: Entra ID as the company "front desk"

Employee Login Front desk (verify) Entra ID Microsoft 365 Allow Business apps Allow The front desk verifies identity, then lets only authorized people through to each service
← Scroll horizontally →

Entra ID acts as the "company front desk," verifying identity and letting only authorized people through to each service.

Diagram

Before / after: password only → MFA

Conventional (password only) Entra ID (MFA) Employee Password only Impersonation If leaked If the password leaks, anyone can impersonate the user One secret only. If stolen, anyone can get in Employee Password + phone Genuine user only Verify identity with password + phone approval Even if the password leaks, no entry without the phone in hand
← Scroll horizontally →

A password-only login can be impersonated if leaked. MFA (multi-factor authentication) adds a phone approval on top of the password to verify identity and prevent impersonation.

Diagram

Step by step: Conditional Access

1 Login request Employee access 2 Verify identity Password + MFA 3 Assess context Location/device/risk 4 Allow / block Step-up if risky Allow Block Beyond identity, it weighs location, device, and risk: allow if fine, step-up or block if suspicious
← Scroll horizontally →

Conditional Access assesses location, device, and risk in addition to identity, then automatically allows safe access or requires step-up authentication or blocks suspicious access.

Pros

Benefits

  • Centrally manage employee accounts, reducing operational effort and oversights.
  • With SSO, a single login covers multiple services, improving convenience.
  • MFA helps prevent impersonation if a password is leaked.
  • Instantly disable a departing employee's account and cut off access to all services.
  • Access logs support auditing and investigation.
Cons

Drawbacks and considerations

  • !An initial identity integration design (cleaning up existing accounts) is required.
  • !You need to understand the licensing model (the difference between Microsoft 365 standard features and add-ons).
  • !Appropriate operational rules and administration skills are required.
  • !When introducing MFA, advance communication to employees and guidance on usage are needed.
How to Start

Adoption path (a typical approach)

Switching the entire company over all at once causes confusion. A realistic approach is to assess the current state and proceed in stages.

STEP 1PROCESS
Assess the current state Inventory the services in use and existing accounts, and confirm who is using which service.
InventoryActual usage
STEP 2PROCESS
Identity integration Consolidate scattered accounts into Entra ID and tie together logins to your services.
ID consolidationSSO
STEP 3PROCESS
Enable multi-factor authentication Enable MFA and move to logins that no longer rely on passwords alone. Provide usage guidance to employees.
MFAEmployee comms
STEP 4PROCESS
Configure conditional access Set up access controls based on location, device, and risk to curb suspicious logins.
Access controlPolicy
STEP 5PROCESS
Operation and review Review access rights while monitoring logs, and keep accounts in order as people join and leave.
Permission reviewOperational rules
Model Case

An adoption scenario for a mid-sized company

This is a hypothetical model case based on inquiries we frequently receive. The actual approach and results vary depending on the environment.

Case

A company with ~400 employees (multiple locations)

Challenge: The number of cloud services in use has grown, and managing separate IDs and passwords for each service has become cumbersome. With more locations and remote workers, there is concern about whether departing employees' accounts have been removed from all services.

Existing environment: Microsoft 365 is in use. Account management is handled individually per service, and disabling accounts on departure is done manually.

Before HQ Branch Remote Separate ID per service IDs and passwords scattered per service; departures hard to manage After HQ Branch Remote Entra ID Allowed app Allow Unauthorized Block Entra ID centralizes IDs; secure with SSO and MFA
  • 1Consolidate employee accounts in Entra ID and centrally manage logins to multiple services.
  • 2With SSO, a single login enables use of multiple services.
  • 3Enable MFA to reduce the risk of impersonation.
  • 4On departure, disable the ID and instantly cut off access to all services.

Results: Logging in to each service became simpler, and a departing employee's account can now be cut off from all services in a single action. It also became possible to record who accessed what.

* The above is a hypothetical model case. The actual configuration and results vary depending on your environment.

FAQ

Frequently Asked Questions

  • QWhat is Entra ID (formerly Azure AD)?
    Microsoft Entra ID is a cloud identity platform that centrally manages employee accounts (IDs) and ties together logins to Microsoft 365 and a wide range of cloud services. It is the foundation for controlling who can access which service, and it also serves as the starting point for SASE and Zero Trust.
  • QWhat are SSO, MFA, and conditional access?
    SSO (single sign-on) lets a single login use multiple services directly. MFA (multi-factor authentication) combines a password with an approval on a smartphone, for example, to prevent impersonation. Conditional access automatically controls whether access is allowed and whether additional authentication is required, based on location, device, and risk.
  • QDo you need it if you already use Microsoft 365?
    Even if Microsoft 365 is already in use, managing separate IDs and passwords per service tends to become cumbersome. By managing accounts centrally with Entra ID, you can tie together logins to multiple services and cut off a departing employee's account from all services in a single action.
  • QCan mid-sized companies adopt it?
    Yes. Because switching the entire company over all at once causes confusion, a realistic approach is to proceed in stages: assess the current state, integrate identities, enable MFA, configure conditional access, and operate. We also present a hypothetical model case of a company with about 400 employees across multiple locations.
  • QWhat are the benefits and considerations of adoption?
    The benefits include centralized account management, improved convenience through SSO, prevention of impersonation with MFA, instant disabling of departing employees' accounts, and audit support via access logs. On the other hand, you need an initial identity integration design, an understanding of the licensing model, appropriate operational rules and administration skills, and advance communication to employees when introducing MFA.

Consult us about rethinking identity management

From challenges such as "managing IDs and passwords per service is cumbersome," "we are uneasy about managing departing employees' accounts," or "we want to introduce MFA," we support an overall review that includes Entra ID.

Contact us