Microsoft Entra Admin Center Overview & Navigation
SC-300 Exam Alignment
SC-300
Implement and manage user identities: Understand the Microsoft Entra admin center interface, tenant properties, directory configuration, Entra ID edition capabilities, and how to connect administrative tools via Microsoft Graph PowerShell.
- Know the URL for the Microsoft Entra admin center and understand how it differs from the classic Azure portal
- Identify which Entra ID edition is required for key features — especially Conditional Access (P1) and PIM (P2)
- Know the left navigation structure: Identity, Protection, Governance, Workload identities, External Identities, Monitoring & health, Settings
- Understand that Microsoft Graph PowerShell has replaced the deprecated Azure AD PowerShell module
🌐 Microsoft Entra Admin Center Interface
The Entra admin center replaced the older Azure AD blade in the Azure portal. It provides a cleaner, dedicated experience for identity administration. The URL is entra.microsoft.com.
entra.microsoft.com › Home
Key Navigation Sections
| Section | What You Find Here | Key Admin Tasks |
|---|---|---|
| Identity | Users, Groups, Devices, App registrations, Enterprise applications, Roles & admins, Administrative units | Create users, manage groups, assign roles, register apps |
| Protection | Conditional Access, Authentication methods, Password reset (SSPR), Identity Protection, Risky users & sign-ins | Build CA policies, configure MFA methods, enable SSPR, review risky sign-ins |
| Governance | Access reviews, Entitlement management, Privileged Identity Management (PIM), Terms of use, Lifecycle workflows | Create access reviews, manage JIT role activation, configure entitlement packages |
| Workload identities | Service principals, App registrations credentials and permissions, Workload identity federation | Manage app credentials, review app permissions, configure federation |
| External Identities | B2B collaboration, Cross-tenant access settings, External collaboration settings, User flows | Configure guest access, set up cross-tenant access policies |
| Monitoring & health | Sign-in logs, Audit logs, Provisioning logs, Workbooks, Diagnostic settings, Identity Secure Score | Diagnose sign-in failures, export logs, review security score |
| Settings | Tenant properties, User settings, Group settings, External user settings | Configure tenant-wide defaults for user and group management |
📋 Entra ID Editions & Licensing
Microsoft Entra ID is available in four editions. Understanding which edition unlocks which features is critical for the SC-300 exam and for real-world planning.
| Feature | Free | P1 | P2 | Governance |
|---|---|---|---|---|
| Included with | All M365 / Office 365 plans | M365 Business Premium, E3, EMS E3 | M365 E5, EMS E5 | Standalone add-on |
| User & group management | ✅ | ✅ | ✅ | ✅ |
| MFA (per-user and Security Defaults) | ✅ | ✅ | ✅ | ✅ |
| Conditional Access | ❌ | ✅ | ✅ | ✅ |
| SSPR (Self-Service Password Reset) | ❌ | ✅ | ✅ | ✅ |
| Dynamic group membership | ❌ | ✅ | ✅ | ✅ |
| Group-based licensing | ❌ | ✅ | ✅ | ✅ |
| Administrative Units | ❌ | ✅ | ✅ | ✅ |
| Custom roles | ❌ | ✅ | ✅ | ✅ |
| Privileged Identity Management (PIM) | ❌ | ❌ | ✅ | ✅ |
| Identity Protection (risk policies) | ❌ | ❌ | ✅ | ✅ |
| Access Reviews | ❌ | ❌ | ✅ | ✅ |
| Entitlement Management | ❌ | ❌ | ❌ | ✅ |
| Lifecycle Workflows | ❌ | ❌ | ❌ | ✅ |
⚠️ Licence Assignment Requirement
For P1 and P2 features to work for a user, that user must be assigned an Entra ID P1 or P2 licence. If a Conditional Access policy targets a user who doesn't have a P1 licence, the policy may not be enforced correctly for that user. Licence assignment can be done directly to users or via group-based licensing (P1 feature itself).
🔧 Tenant Properties & Overview
The tenant overview (Identity → Overview) shows essential information about your Entra directory:
| Property | Description | Where Used |
|---|---|---|
| Tenant ID | A globally unique identifier (GUID) for your directory | Required for API calls, Graph PowerShell connections, cross-tenant federation |
| Primary domain | The initial domain created when the tenant was set up (e.g., contoso.onmicrosoft.com) | Default UPN suffix for new users |
| Custom domains | Verified custom domains added and verified via DNS (e.g., contoso.com) | Used as UPN suffix, email domain |
| Directory ID | Same as Tenant ID — used interchangeably | Azure resource management, ARM templates |
| Edition | Shows which Entra ID licence is active | Determines which features are available |
💻 Microsoft Graph PowerShell
The Microsoft Graph PowerShell SDK is the official, supported PowerShell module for managing Entra ID. The older Azure AD PowerShell (AzureAD module) and MSOnline modules are deprecated as of March 2024 and will be removed — all scripts must be migrated to Microsoft Graph PowerShell.
# Install the Microsoft Graph PowerShell SDK Install-Module Microsoft.Graph -Scope CurrentUser # Connect to Microsoft Graph (specify scopes needed) Connect-MgGraph -Scopes 'User.ReadWrite.All','Group.ReadWrite.All','Directory.ReadWrite.All' # Check the connected tenant and current permissions Get-MgContext # Get tenant overview information Get-MgOrganization | Select-Object DisplayName,Id,TenantType,VerifiedDomains # List all verified domains on the tenant (Get-MgOrganization).VerifiedDomains | Select-Object Name,IsDefault,IsInitial,Type # Disconnect when done Disconnect-MgGraph
💡 Azure AD PowerShell vs Microsoft Graph PowerShell
- AzureAD module (Connect-AzureAD, Get-AzureADUser): Deprecated March 2024, being removed
- MSOnline module (Connect-MsolService): Also deprecated, older module
- Microsoft.Graph module (Connect-MgGraph, Get-MgUser): Current, supported, recommended
- Microsoft Graph PowerShell uses permission scopes — you specify exactly what permissions you need. This aligns with least-privilege access and is audited in sign-in logs as service principal activity
💡 Best Practices
- Bookmark entra.microsoft.com as the primary identity admin portal — avoid using the Azure portal Azure AD blade which is being phased out
- Verify your Entra ID edition before planning identity features — many key security features (Conditional Access, PIM, Identity Protection) require P1 or P2 licences
- Migrate all Azure AD PowerShell scripts to Microsoft Graph PowerShell now — the deprecated modules will be removed and scripts will break without warning
- Use the least-privilege scopes when connecting via Graph PowerShell — only request the permissions your script needs, not Directory.ReadWrite.All for a read-only task
- Create a dedicated break-glass Global Administrator account that is excluded from all Conditional Access policies — this ensures you can always recover access in an emergency
🎓 Interview Q&A
Your organisation wants to implement Conditional Access policies requiring MFA for all users. A colleague says the Entra ID Free licences included with their Microsoft 365 Business Essentials subscription are sufficient. Is this correct?
An administrator needs to configure Privileged Identity Management (PIM) to enable just-in-time activation of the Global Administrator role. Which Entra ID edition is required?
A team is migrating existing Azure AD PowerShell scripts to a supported module. They currently use Connect-AzureAD and Get-AzureADUser. What is the correct replacement?
Where in the Microsoft Entra admin center would you find Conditional Access policies?
An administrator wants to run a Microsoft Graph PowerShell script that reads user sign-in logs. They run Connect-MgGraph with no scopes specified. What happens?