Popular 3rd-Party Tools:

• MigrationWiz (by BitTitan):

• Cloud-based migration tool.
• Easy-to-use interface.
• Supports mailbox, document, archive, and public folder migrations.
• Pre-stage, delta sync, scheduling, and email coexistence features.
• Quest On Demand Migration / Quest Migration Manager:
• Offers robust reporting and scheduling options.
• Good for large enterprises and staged migrations.
• Supports tenant-to-tenant migrations too.
• CodeTwo Office 365 Migration:
• Easy GUI, supports Exchange to Office 365 migration.
• Includes delta sync, scheduling, and filtering options.
• SkyKick Migration Suite:
• Full-service migration platform.
• Includes migration of Outlook profiles, PSTs, permissions, and more.
• White-labeled by many MSPs.
• TransVault:
• Advanced archiving and compliance-focused migration.
• Great for legacy email archive migrations to Microsoft 365.
• Kernel Migrator for Exchange:
• Supports Exchange and Office 365 migrations.
• Offers pre-migration analysis, real-time progress monitoring.

3. How do you ensure minimal downtime or user impact during migration?

• User Communication and Training:
• Notify users ahead of time.
• Share documentation about what to expect before, during, and after
migration.
• Conduct pilot migrations for key users.
• Pre-staging and Delta Sync:
• Use tools (e.g., MigrationWiz, SkyKick) to pre-stage data.
• Delta syncs ensure that only recent changes are migrated during the
cutover.
• Scheduling Smartly:
• Perform cutovers during non-business hours (e.g., weekends, nights).
• Avoid business-critical times like quarter/year-end.
• Email Coexistence:
 • Enable free/busy sharing and calendar visibility between on-prem and
online users in hybrid.
• Testing:
• Always test with a few mailboxes before performing full migration.
• Validate Outlook connectivity, Autodiscover, and mobile access post-
migration.
1. Cutover Migration

Best For: Small organizations (less than 2,000 mailboxes)

Process:
Moves all mailboxes, contacts, and distribution groups at once.
Ideal for organizations using Microsoft Exchange 2003, 2007, 2010, or 2013.
Requires DNS records to be updated after migration.
Users may need to recreate their Outlook profiles after migration.
Pros: Simple and quick for small businesses.
Cons: Not suitable for large organizations due to downtime.
2. Staged Migration

Best For: Medium-sized organizations with more than 2,000 mailboxes.

Process:
Migrates mailboxes in batches over time.
Supports Exchange 2003 and 2007 but not newer versions.
Requires directory synchronization using Azure AD Connect.
Pros: Minimizes downtime and allows a phased approach.
Cons: Limited to older Exchange versions and requires more management.
3. Hybrid Migration

Best For: Large enterprises that want to maintain coexistence between an

on-premises Exchange server and Office 365.
Process:
Allows seamless integration between on-premises Exchange and Office 365.
Supports Exchange 2010, 2013, 2016, and 2019.
Users can move mailboxes gradually without disruption.
Uses Azure AD Connect for identity synchronization.
Pros: Enables long-term hybrid scenarios, provides flexibility.
Cons: Complex setup, requires advanced IT knowledge and infrastructure.
4. IMAP Migration

Best For: Organizations using non-Exchange email systems (e.g., Gmail,

Yahoo, or any IMAP-supported email provider).
Process:
Transfers only email messages, not contacts, calendar items, or tasks.
Requires admin access to the IMAP source system.
Users need to manually migrate other data like contacts and calendars.
Pros: Works with many different email platforms.
Cons: Limited to emails; manual effort needed for full data migration.
5. Third-Party Migration Tools

For organizations needing more advanced migration capabilities, third-party

tools offer automation, speed, and support for various data types. These
tools help migrate:

Emails, contacts, and calendars from various platforms.

SharePoint sites and document libraries.
OneDrive and Teams data.
microsoft interviw questions
Popular Third-Party Migration Tools:

Microsoft FastTrack: Free for eligible Microsoft 365 customers.

BitTitan MigrationWiz: Cloud-based, supports multiple data sources.
Quest Migration Manager: Advanced migration and coexistence options.
ShareGate: Best for SharePoint and OneDrive migrations.
CloudM: Automates large-scale migrations with security and compliance.
Pros: Simplifies migration, minimizes downtime, and supports multiple data
types.
Cons: Some tools require licensing costs.

Now let’s break down what’s being phased out and what’s replacing it:

1. MSOL (MSOnline Module)

• Status: Deprecated (still functional, but unsupported)
• Used For: Managing users, groups, licenses
• Replaced By: Microsoft Graph PowerShell SDK
• Why: MSOL uses legacy APIs, lacks modern authentication and granular
permissions

2. AzureAD / AzureADPreview Modules

• Status: Deprecated
• Used For: Directory tasks, user/group management
• Replaced By: Microsoft Graph PowerShell SDK
• Why: Graph supports fine-grained scopes, cross-platform scripting, and
future features
3. AzureRM Module
• Status: Fully retired
• Replaced By: Az Module
• Why: Az is cross-platform, standardized, and aligned with modern Azure
services

What’s New?
Microsoft Graph PowerShell SDK
This is now the standard tool for Microsoft 365 automation. It works with
Microsoft Graph — the single API surface for Exchange, Teams, SharePoint,
Azure AD, and more.

Benefits of Microsoft Graph:

• Modern OAuth 2.0 authentication
• Fine-grained permissions with delegated/admin scopes
• Cross-platform support (Windows, Mac, Linux)
• Continually updated and aligned with Microsoft’s future roadmap

Tip to Stand Out in Interviews:

“Since Microsoft is sunsetting older modules like MSOL and AzureAD, I’ve
already started migrating my scripts to Microsoft Graph SDK. For example, I
use Get-MgUser and Get-MgGroup for user/group management now, and I
build automation with future support in mind.”

Slide this kind of awareness into any relevant answer — it shows you’re
proactive, updated, and thinking long-term.

Step 1: Know the Fundamentals

Before you jump into big scripts, be comfortable with:
• Get-Mailbox, Get-MailboxStatistics, Get-TransportRule
• Where-Object, Select-Object, and piping | to filter results
• Handling arrays, loops, and if-else conditions

Tip: Interviewers often ask you to write or explain a script live.

⸻

Step 2: Real-World Scenarios (This is what they ask!)

Here’s how they frame questions:
• “How would you find all users with mailbox size > 50GB?”
Use: Get-MailboxStatistics + Where-Object
• “Write a script to assign licenses to all unlicensed users.”
Combine: Get-MsolUser, Where, Set-MsolUserLicense
• “How do you trace an email for delivery issues using PowerShell?”
Use: Get-MessageTrace and Get-MessageTraceDetail

They want to see how you think, not just what you type.

Step 3: Show Hybrid Awareness

If you’re interviewing for Exchange Hybrid roles:
• Be ready to use both Exchange Online PowerShell and on-prem EMS
• Commands like Get-HybridConfiguration, Get-InboundConnector, Get-
OutboundConnector are crucial
• Know how to check centralized transport:
Get-HybridConfiguration | Select CentralizedTransportEnabled

Step 4: Bonus – Automate Your Troubleshooting

A simple script that logs mailbox permissions, or alerts when a user’s
mailbox crosses a limit, can make you stand out.

When Interviewer Asks: “Which would you choose and why?”

Answer is...
“If the organization wants to keep some mailboxes on-prem for the
foreseeable future and needs a seamless experience, I’d go with Full Hybrid.
But if the goal is a one-time migration with no long-term on-prem
dependency, Minimal Hybrid is faster and simpler.”

Exchange Hybrid Deep Dive – Full vs Minimal Hybrid Mode

When setting up a hybrid Exchange environment between on-premises
Exchange and Microsoft 365, one critical decision is choosing between Full
Hybrid and Minimal Hybrid mode. Each has its use case and purpose,
depending on how your organisation plans to manage coexistence and
migration.
Full Hybrid Mode is designed for long-term coexistence. It provides a rich,
seamless experience across on-prem and cloud, including secure mail
routing, global address list synchronization, calendar free/busy sharing, and
support for OAuth-based authentication. This mode is ideal when some
mailboxes will remain on-prem, or when you need deep integration and
control.

On the other hand, Minimal Hybrid Mode is a lightweight setup aimed at

organisations that simply want to migrate their mailboxes to the cloud
quickly. It supports basic mail flow and creates the required migration
endpoint but doesn’t include advanced features like GAL sync or free/busy
sharing. It’s faster to configure and easier to manage, but it's not suitable for
long-term hybrid needs.
Choosing the right mode depends on your migration strategy. If you're
looking for quick migration, go Minimal. For a long-term hybrid approach, Full
Hybrid is the way to go.

Step-by-Step: How to Set Up Hybrid Exchange (Classic Full Hybrid), For those
connecting on-prem Exchange with Microsoft 365 👇
1️⃣ Prepare Your On-Prem Exchange Server Open firewall ports (25, 443)
2️⃣ Run the Hybrid Configuration Wizard (HCW) once Download from:
https://lnkd.in/gEgT2WNY. Sign in with both on-prem and Microsoft 365
global admin credentials Choose Full or Minimal Hybrid Mode
3️⃣ Configure Key Options in HCW like Mail Flow, Calendar/Free-Busy Sharing,
Secure Mail Routing
4️⃣ HCW Automatically Creates Connectors, Configures Organization
Relationships and Enables OAuth for secure communication
5️⃣ Validate Everything like Test mail flow (cloud ↔ on-prem), Test calendar
availability Confirm migration readiness
6️⃣ Begin Migration (if needed) Move mailboxes using Migration Batches

🧠 Pro Tips:
🔒 Use a trusted SSL cert
🛠 Run HCW with elevated permissions
📡 Keep DNS and Autodiscover correct
 Mail Flow in Microsoft 365 – Centralised vs. Decentralised + How to Check
Yours 🔄

In hybrid environments, email routing can either be centralised or

decentralised — and understanding the difference is key to managing
compliance, mail flow, and performance. 🧠 What's the difference?

📍 Centralised Mail Flow:

All emails (inbound and outbound) pass through your on-prem Exchange
server, even if the mailboxes are in Microsoft 365.
Best for: Organisations with strict compliance, custom security policies, or
DLP requirements.
➕ Pros: Greater control & visibility; Apply custom transport rules easily
➖ Cons: More complexity; On-prem dependency

📍 Decentralised Mail Flow (Cloud-Only):

Emails flow directly between Microsoft 365 and the internet. On-prem
Exchange is not involved in routing.
Best for: Cloud-first orgs, or when simplifying infrastructure is the goal.
➕ Pros: Easier setup and maintenance; No on-prem mail flow bottleneck
➖ Cons: Limited control for some compliance scenarios

🔍 There is five way to check your mail flow type

🧭 1. Exchange Admin Center → Mail Flow → Connectors, Look for connectors
to and from on-prem Exchange → Centralised
⚙️2. Hybrid Configuration Wizard (HCW) If “Route all internet-bound mail
through on-prem” is selected → Centralised
🌐 3. MX Records (DNS):- If MX points to on-prem → Centralised or MX points
to https://lnkd.in/g4rZxpn9 → Decentralised
📩 4. Message Trace:- If Mail hops through on-prem Exchange → Centralised
else Direct M365 delivery → Decentralised
💻 5. PowerShell Quick Check

Connect-ExchangeOnline
Get-InboundConnector
Get-OutboundConnector
Get-HybridConfiguration
Look for: CentralizedTransportEnabled = True
From: 🔹 Real-world interview scenarios 🔹 Common questions around tenant-
to-tenant migrations 🔹 Navigating Exchange Hybrid setups
🔹 Deep-dives into Microsoft Teams architecture 🔹 Best practices for
SharePoint Online migration 🔹 And even behavioural + mindset tips

This series is my small way of giving back to the incredible community I’ve
worked with.
💡 First post is already live — more coming soon! Got a specific topic or
challenge you’d like me to cover? Drop a comment or message me directly.