Explain various steps involved in express migration

 

Explain various steps involved in express exchange migration

Express migration is a way to migrate email data from an on-premises Exchange server to Microsoft 365 or Office 365. Here are the steps involved in an express migration 

1. Verify your ownership of an on-premises domain.
2. Create a migration endpoint to connect Exchange to Microsoft 365 or Office 365.
3. Use the Exchange Admin Center (EAC) to move mailboxes.
4. Remove completed migration batches.
5. Re-enable offline access for Outlook on the web.
6. Start the migration process.

Various steps involved in Hybrid Exchange migration

Various steps involved in Hybrid Exchange migration

A hybrid migration is a way to migrate email data from an on-premises Exchange server to Microsoft 365 or Office 365. Here are the steps involved in a hybrid migration 

1. Verify your ownership of an on-premises domain.
2. Create a migration endpoint to connect Exchange to Microsoft 365 or Office 365.
3. Enable the MRSProxy service.
4. Use the Exchange Admin Center (EAC) to move mailboxes.
5. Remove completed migration batches.
6. Re-enable offline access for Outlook on the web.
7. Start the migration process.
8. Sync your directories to create users.
9. Assign Microsoft 365 licenses to your users.
10. Start migrating user data.
11. Update DNS records.

Various steps involved in staged exchange migration

 

Various steps involved in staged exchange migration 

A staged migration is a way to migrate email data from an on-premises Exchange server to Microsoft 365 or Office 365. Here are the steps involved in a staged migration 

1. Verify your ownership of an on-premises domain.
2. Create a migration endpoint to connect Exchange to Microsoft 365 or Office 365.
3. Create a CSV file that contains a row for each user whose on-premises mailbox will be migrated in the migration batch.
4. Create the staged migration batch.
5. Begin the staged migration batch.
6. Route your MX records to Microsoft 365 or Office 365 mailboxes.
7. Delete your staged migration batch.
8. Assign licenses to your users’ migrated Microsoft 365 or Office 365 accounts.

The main steps you perform for a staged migration are shown in the following illustration 

Various steps involved in cut over migration

Various steps involved in cut over migration


A cutover migration is a way to migrate email data from an on-premises Exchange server to Microsoft 365 or Office 365. Here are the steps involved in a cutover migration

Verify your ownership of an on-premises domain.
Create a migration endpoint to connect Exchange to Microsoft 365 or Office 365.
Create the cutover migration batch.
Begin the cutover migration batch.
Route your MX records to Microsoft 365 or Office 365 mailboxes.
Delete your cutover migration batch.
Assign licenses to your users’ migrated Microsoft 365 or Office 365 accounts.


The main steps you perform for a cutover migration are shown in the following illustration

Types of Email migration setup in M365

 

Types of Email migration setup in M365 

1.Perform a remote move (hybrid) migration 

2.Migrate users from Google Workspace (formerly G Suite)

3.Migrate users from Gmail or  another IMAP system 

4.Import .pst files directly to Exchange online 

5.Perform a cutover Exchange migration 

6.Perform a staged Exchange migration 

7.Migrate from one Microsoft 365 tenent to another 

Available Migration types in M365

 Available Migration types  in M365

There are several types of migrations available in Microsoft 365. 

Here are some of the most common types:

1. Cutover migration: This type of migration is used when you want to migrate all mailboxes at once from an existing on-premises Exchange Server environment to Microsoft 365 or Office 365 
2. Staged migration: This method is suitable for medium-sized companies, particularly those with more than 2,000 mailboxes, that are currently using on-premises Microsoft Exchange 2003 or 2007 
3. Hybrid migration: This type of migration is used when you want to move some mailboxes to Microsoft 365 or Office 365 and keep others on your on-premises Exchange Server 
4. Express migration: This type of migration is used when you want to migrate all mailboxes at once from an existing on-premises Exchange Server environment to Microsoft 365 or Office 365 

List of Pillars of Zero Trust model

 

List of Pillars of Zero Trust model

Based on the principle of "never trust, always verify," Zero Trust helps secure corporate resources by eliminating unknown and unmanaged devices and limiting lateral movement. Implementing a true Zero Trust model requires that all components (identity, endpoints, apps, infrastructure, networking and data) be validated and proven trustworthy.

Identity

When an identity attempts to access a resource, verify that identity with strong authentication, and ensure access is compliant and typical for that identity.

Endpoints

Monitor and enforce device health and compliance for secure access.

Apps

Apply controls and technologies to discover shadow IT, ensure appropriate in-app permissions, gate access based on real-time analytics, monitor for abnormal behavior, control user actions, and validate secure configuration options.

Infrastucture

Use telemetry to detect attacks and anomalies, automatically block and flag risky behavior, and take protective actions.

Networking

Segment networks (and do deeper in-network micro-segmentation) and deploy real-time threat protection, end-to-end encryption, monitoring, and analytics.

Data

Classify, label, and encrypt data, and restrict access based on those attributes.

List of Tasks to be reviewed and completed before M365 Initial Setup

List of Tasks to be reviewed and completed before M365 Initial Setup 


Check network readiness

Make sure your network's environment is prepared for optimal use with Microsoft 365 services.

Connect your domain

Connect a domain you own (for example, contoso.com) or purchase a new domain for simplified sign-in with company email addresses. We'll provide you with the necessary DNS records for your domain to work with your Microsoft 365 services.

Add users

Add users in bulk or one at a time. If you have on-premises Active Directory, set up Azure Active Directory Connect (Azure AD Connect) to sync your users.

Assign licenses

Assign licenses to users individually or in groups from within Azure Active Directory (Azure AD).

Tasks required before setting up M365

 

Tasks required before setting up M365

Before setting up Microsoft 365, there are several tasks that you should complete to ensure a smooth deployment. Here are some of the tasks that you should consider:

1. Prepare your environment: Before you start using Microsoft 365, turn on basic features and strengthen the security of your data in the Microsoft cloud 
2. Set up connectors: Make sure you have completed the following tasks in Microsoft 365 or Office 365: To set up connectors, you need permissions assigned before you can begin 
3. Ensure appropriate licensing: Ensure that you have the appropriate Azure subscriptions and M365/O365 licensing for your organization. You must use paid Azure Subscriptions. Subscriptions you got through Free, Trial, Sponsorships, MSDN Subscriptions, and those under Legacy Support are not eligible 

Tasks required before setting up cloud services

 

Tasks required before setting up cloud services

Before setting up cloud services, there are some tasks that you should complete to ensure a successful deployment. Here are some of the tasks that you may need to do 

1. Assess your current environment: You should evaluate your existing workloads, applications, data, and infrastructure to determine which ones are suitable for migration to the cloud and which ones need to be redesigned or rebuilt.
2. Choose a cloud provider and service model: You should compare different cloud providers and service models (such as IaaS, PaaS, or SaaS) to find the best fit for your business needs and budget. You should also consider the security, reliability, scalability, and compatibility of the cloud services that you want to use.
3. Plan your migration strategy: You should plan how you will migrate your workloads, applications, data, and infrastructure to the cloud. You should also consider how you will manage the migration process, such as choosing the right tools, testing the migration, and monitoring the performance and availability of the cloud services.
4. Design your cloud architecture: You should design your cloud architecture based on the best practices and recommendations of your cloud provider. You should also consider how you will optimize your cloud architecture for performance, security, availability, and cost.
5. Build your cloud team: You should build a cloud team with the right skills and roles to manage and operate your cloud services. You should also define the responsibilities and tasks of each team member and provide them with the necessary training and tools.
6. Implement security and governance policies: You should implement security and governance policies to protect your cloud services and data from unauthorized access and misuse. You should also comply with the relevant regulations and standards for your industry and location.
7. Monitor and optimize your cloud services: You should monitor and optimize your cloud services to ensure that they are running smoothly and efficiently. You should also troubleshoot any issues that may arise and implement backup and disaster recovery plans.

How to migrate M365 from older domain to new domain

 
How to migrate M365 from older domain to new domain

To migrate Microsoft 365 from an older domain to a new domain, you can transfer your domain from Microsoft to another domain registrar . Here are the steps to transfer your domain:

1. In the admin center, go to Settings > Domains.
2. On the Domains page, select the Microsoft 365 domain that you want to transfer to another domain registrar, and then select Check health.
3. At the top of the page, select Transfer domain.
4. On the Choose where to transfer your domain page, select A different registrar, and then click Next.

Please note that you can’t transfer a Microsoft 365 domain to another registrar for 60 days after you purchase the domain from Microsoft 

If you purchased your domain name from Microsoft and they are still hosting it for you, you have to transfer your domain name from Microsoft to a third-party vendor 

Alternatively, you can transfer data manually between two accounts by setting up your custom domain for your new subscription and creating users with email addresses on your custom domain 

Different type of M365 Update channels

 Different type of M365 Update channels

Microsoft 365 Apps for Enterprise offers three production update channels for you to choose from :

1. Current Channel: This channel provides users with the latest features and updates as soon as they are released. It is recommended for users who want to stay up-to-date with the latest features and improvements.

2. Monthly Enterprise Channel: This channel provides users with new features and updates on a monthly basis. It is recommended for users who want to stay up-to-date with the latest features but prefer a slower update cadence.

3. Semi-Annual Enterprise Channel: This channel provides users with new features and updates every six months. It is recommended for users who want to stay up-to-date with the latest features but prefer a slower update cadence and more time to test new features before they are released.

You can switch between these channels using group policy settings or servicing profiles 

Different ways to deploy Microsoft 365 Apps

 

Different ways to deploy Microsoft 365 Apps 

There are different ways to deploy Microsoft 365 Apps depending on your organization’s needs. Here are some of the most common methods:

1. Cloud-based deployment: This is the recommended method for deploying Microsoft 365 Apps. You can deploy Microsoft 365 Apps from the cloud using the Microsoft Endpoint Manager portal or Microsoft Intune 

2. Local source deployment: You can also deploy Microsoft 365 Apps from a local source on your network using Microsoft Endpoint Manager Configuration Manager 

3. Zero content deployment: This method involves downloading the source files and hosting them on a UNC path. You can then package them and deploy them from Microsoft Endpoint Manager Configuration Manager 

It’s important to note that each deployment method has its own advantages and disadvantages. For example, cloud-based deployment is easier to manage and update, but local source deployment gives you more control over the installation process 

Pros and Cons of M365 Updates from on-premises locations

 

Pros and Cons of M365 Updates from on-premises locations

Here are some pros and cons of updates from on-premises locations:

Pros:

1. Control: With on-premises updates, you have more control over when and how updates are applied .
2. Security: On-premises updates can be more secure than cloud-based updates because they are not exposed to the internet 
3. Customization: On-premises updates can be customized to meet specific business needs 

Cons:

1. Cost: On-premises updates can be more expensive than cloud-based updates because of the cost of hardware, software, and maintenance 
2. Scalability: On-premises updates can be more difficult to scale than cloud-based updates because they require additional hardware and software 
3. Maintenance: On-premises updates require more maintenance than cloud-based updates because they require hardware and software maintenance 

It’s important to note that the decision between on-premises and cloud-based updates depends on your specific business needs. While on-premises updates offer more control and customization, they can also be more expensive and difficult to scale. Cloud-based updates offer more scalability and lower costs, but may not offer the same level of control and customization as on-premises updates.

Considerations using the cloud as your update source

Considerations using the cloud as your update source

When using the cloud as your update source, there are some considerations that you should keep in mind:

1. Network connectivity: Devices must be able to connect to the Office CDN. For this, the URLs and IPs listed in Office 365 URLs and IP address ranges must be accessible for devices 
2. Cost: The cost of storage in Azure can be significantly lower than the cost of maintaining storage with similar characteristics in an on-premises data center
3. Elastic scale: Planning and managing data capacity growth in an on-premises environment can be challenging, particularly when data growth is difficult to predict
4. Disaster recovery: Cloud-based software can offer quick disaster recovery and backup

In addition to these considerations, cloud-based software can also offer reduced costs, more flexibility and scalability, mobility, improved collaboration, enhanced data security, and a reduced carbon footprint for a better environment

Core benefits of using cloud as update source

 

Core benefits of using cloud as update source

There are two core benefits when leveraging the cloud as your update source:

1. Delta updates: When the Microsoft 365 Apps pull the latest updates, only the difference between the currently installed release and the targeted one is downloaded. This can reduce the amount of data that needs to be downloaded and can save time
2. Automatic updates: With cloud-based software, updates are automatically installed by the provider. This means that you don’t have to worry about manually updating your software or missing important security patches

how to deliver updates for the Microsoft 365 Apps

 

how to deliver updates for the Microsoft 365 Apps

• Using the cloud for updates
• Automatic Updates or Microsoft Intune
• Servicing Profiles
• 
  
• Using on-premises locations for updates
• Microsoft Configuration Manager
• Network shares
• 
  
• Combining cloud and on-premises locations for updates (hybrid)
  • Microsoft Configuration Manager

Different Methods of Managing M365 Updates

  

How to manage M365 updates:

• Update automatically: Client devices are automatically updated directly from the Office CDN based on the update channel you define as part of the initial deployment.

• Manage updates with Intune: Use Intune to set policies on devices, which control how and when those should get updates from the cloud.

• Manage updates with a servicing profile: When using the Monthly Enterprise Channel, a servicing profile gives you the most comprehensive toolset to manage updates from the cloud.

• Manage updates with Configuration Manager: Updates are downloaded and deployed to client devices by Configuration Manager.

• Manage updates with the Office Deployment Tool: Updates are downloaded to a local source by the ODT and then installed on client devices.

Practical Deployment Methods of M365

 

Practical Deployment Methods of M365

• Self-install from the cloud: Manage your deployment from the Microsoft 365 portal and have your users install the apps on their client devices directly from the portal.

• Deploy from the cloud using Intune: Manage your deployment through Intune and automate the configuration and installation of the Microsoft 365 Apps.

• Deploy from a local source with Configuration Manager: Manage your deployment with Configuration Manager, and download and deploy from distribution points on your network.

• Deploy from the cloud with the Office Deployment Tool: Manage your deployment with the ODT, and install on client devices directly from the Office CDN.

• Deploy from a local source with the Office Deployment Tool: Manage your deployment with the ODT, and download and deploy from a local source on your network.

Deployment methods of M365

 Deployment methods of M365

There are several deployment methods for Microsoft 365. Here are some common deployment methods:

1. Cloud-based deployment: This method involves deploying Microsoft 365 Apps from the cloud using the Microsoft 365 portal or Microsoft Intune 
2. Local source deployment: This method involves deploying Microsoft 365 Apps from a local source such as a network share or a local folder 
3. Configuration Manager deployment: This method involves deploying Microsoft 365 Apps using Microsoft Configuration Manager 
4. Windows Autopilot deployment: This method involves deploying Windows 10 devices with Microsoft 365 using Windows Autopilot 

Source hierarchy strategy in Configuration Manager

 
Source hierarchy strategy in Configuration Manager

A source hierarchy is a Configuration Manager hierarchy that has data that you want to migrate. When you set up migration and specify a source hierarchy, you specify the top-level site of the source hierarchy. This site is also called a source site

In Configuration Manager, you can use a source hierarchy strategy to plan how to migrate a supported source hierarchy to a Configuration Manager destination hierarchy. The strategy includes setting up the source hierarchy to use the same network locations or boundaries as your destination hierarchy and installing new clients to your destination hierarchy and using automatic site assignment 

Stages of M365 migration

 

Stages of M365 migration

The stages of a Microsoft 365 migration can vary depending on the migration method used. However, here are some common stages involved in a typical migration:

1. Planning: This stage involves assessing your current environment and identifying the best migration approach for your organization 
2. Preparation: This stage involves preparing your environment for migration by configuring your source and target environments 
3. Migration: This stage involves migrating your data to Microsoft 365 using one of several migration methods 
4. Validation: This stage involves validating that your data has been migrated successfully and that your users can access their data in Microsoft 365 
5. Optimization: This stage involves optimizing your environment for Microsoft 365 by configuring features such as security, compliance, and mobile device management

Concepts used during M365 Migration

 Concepts used during M365 Migration

When migrating to Microsoft 365, there are several concepts that are important to understand. Some of the key concepts include:

1. Data migration process: This refers to the process of moving data from your existing messaging environment to Microsoft 365
2. Migration velocity: This refers to the speed at which data is migrated from your existing messaging environment to Microsoft 365 
3. Migration methods: Microsoft 365 supports several methods to migrate email, calendar, and contact data from your existing messaging environment to Microsoft 365 
4. Migration roadmap: This refers to the plan that outlines the steps involved in migrating your apps and databases with minimal downtime and potential operational and business impact during migration 

Which branch of Configuration Manager should I use?

 

Which branch of Configuration Manager should I use?

There are three branches of Configuration Manager available:

    Current branch,

    Long-term servicing branch

    Technical preview branch 

The Current branch is licensed for use in a production environment and is the preferred installation option for most customers 

The Long-term servicing branch is licensed for use in production for Configuration Manager customers who are using the current branch and have allowed their Configuration Manager Software Assurance (SA) or equivalent subscription rights to expire after October 1, 2016 

The Technical preview branch is intended for testing new features and functionality before they are released in the Current Branch 

Default accounts in M365

 

Default accounts in M365

Microsoft 365 has several default accounts that are created when you sign up for the service. These accounts include:

1. Global administrator account: This account has access to all administrative features in Microsoft 365 
2. SharePoint administrator account: This account has access to all administrative features in SharePoint Online 
3. Exchange administrator account: This account has access to all administrative features in Exchange Online 
4. Skype for Business administrator account: This account has access to all administrative features in Skype for Business Online 

In addition to these default accounts, you can also create custom accounts with specific roles and permissions based on your organization’s needs 

No of Devices configuration in M365

How many devices we can configure in M365?

With Microsoft 365, you can install Office on all your devices and sign in to Office on five devices at the same time. This includes any combination of PCs, Macs, tablets, and phones. With a single license, users can install and activate Microsoft 365 Apps on up to 5 desktops/laptops, 5 tablets, and 5 mobile devices. The actual limitation is that only 5 devices can be logged into Office at any one time.