Cloud Adaptation and SharePoint Server Test Lab Guide for IT Professionals

Use these cloud adoption Test Lab Guides (TLGs) to set up demonstration or dev/test environments for Office 365, Enterprise Mobility + Security (EMS), Dynamics 365, and Office Server products.

TLGs help you quickly learn about Microsoft products. They’re great for situations where you need to evaluate a technology or configuration before you decide whether it’s right for you or before you roll it out to users. The “I built it out myself and it works” hands-on experience helps you understand the deployment requirements of a new product or solution so you can better plan for hosting it in production.

TLGs also create representative environments for development and testing of applications, also known as dev/test environments.

See these additional resources before diving in:

• View the Experience the Microsoft Cloud with Cloud Adoption Test Lab Guides Microsoft Virtual Academy session (only 22 minutes).
• Click here for a visual map to all the articles in the One Microsoft Cloud Test Lab Guide stack.

Office 365 dev/test environment

Use these articles to build your Office 365 dev/test environment:

• Base Configuration dev/test environment

  Create a simplified intranet running in Microsoft Azure infrastructure services. This is an optional step if you want to build a simulated enterprise configuration.

• Office 365 dev/test environment

  Create an Office 365 Enterprise E5 trial subscription, which you can do from your computer or from a simplified intranet running in Azure infrastructure services.

• DirSync for your Office 365 dev/test environment

  Install and configure Azure AD Connect for directory synchronization with password synchronization. This is an optional step if you want to build a simulated enterprise configuration.

For your Office 365 dev/test environment, use these articles to demonstrate enterprise features of Office 365:

• Multi-factor authentication for your Office 365 dev/test environment

  Configure and test secondary authentication using a text message sent to your smart phone for an account in your Office 365 subscription.

• Federated identity for your Office 365 dev/test environment

  Configure and demonstrate federated authentication with the accounts of a Windows Server Active Directory domain.

• Advanced Security Management for your Office 365 dev/test environment

  Configure and demonstrate Advanced Security Management, which allows you to create policies that monitor for and inform you of suspicious activities in your Office 365 subscription.

• Advanced Threat Protection for your Office 365 dev/test environment

  Configure and demonstrate Advanced Threat Protection, which is a feature of Exchange Online Protection (EOP) that helps keep malware out of your email.

• Advanced eDiscovery for your Office 365 dev/test environment

  Add example data and demonstrate Advanced eDiscovery, which allows you to quickly find and analyze the data that is stored in Office 365, including email and documents.

• Sensitive file protection in the Office 365 dev/test environment

  Demonstrate how you can use Office 365 Information Rights Management to protect the data in sensitive documents, even when they are accidentally posted in the wrong document folders.

• Data classification and labeling in the Office 365 dev/test environment

  Demonstrate how the Azure Information Protection client can be used to classify documents with various levels of security.

• Isolated SharePoint Online team site dev/test environment

  Demonstrate how to create a SharePoint Online team site that is isolated from the rest of the organization.

The Microsoft 365 Enterprise dev/test environment

Create a dev/test environment for Microsoft 365 Enterprise scenarios with these articles:

• The Microsoft 365 Enterprise dev/test environment

  Create the initial environment that includes Office 365 E5, Enterprise Mobility + Security (EMS) E5, and a computer running Windows 10 Enterprise.

• MAM policies for your Microsoft 365 Enterprise dev/test environment

  Create user groups and mobile application management (MAM) policies for ioS and Android devices.

• Enroll iOS and Android devices in your Microsoft Enterprise 365 dev/test environment

  Enroll iOS or Android devices and manage them remotely.

Office 365 and Dynamics 365 dev/test environment

Add a Dynamics 365 trial subscription and test Office 365 and Dynamics 365 integrated features and scenarios with these articles:

• Office 365 and Dynamics 365 dev/test environment

  Add a Dynamics 365 trial subscription and Dynamics 365 licences and permissions to your user accounts.

• Exchange Online integration for your Office 365 and Dynamics 365 dev/test environment

  Configure and then demonstrate how Office 365 and Dynamics 365 work together in Exchange Online mailboxes.

The One Microsoft Cloud dev/test environment

Create a dev/test environment that includes all of Microsoft’s cloud offerings: Office 365, Azure, EMS, and Dynamics 365. See The One Microsoft Cloud dev/test environment for the step-by-step instructions.

Simulated cross-premises dev/test environments

You can create a cross-premises dev/test environment, which includes an Azure virtual network and a simulated on-premises network, with these articles:

• Simulated cross-premises virtual network in Azure

  Create a simulated intranet connected to an Azure virtual network in a hybrid cloud configuration.

• Intranet SharePoint Server 2016 in Azure dev/test environment

  Create a single-server SharePoint Server 2016 farm in the Azure virtual network and test connectivity and administration from the simulated on-premises network.

Additional cloud-based dev/test environments

Here are additional cloud-based dev/test environments that you can create in Azure infrastructure services:

• SharePoint Server 2016 dev/test environment in Azure

  Build a single-server SharePoint Server 2016 farm in Azure infrastructure services.

• Exchange 2016 dev/test environment in Azure

  Build a single Exchange 2016 server in Azure infrastructure services.

• SharePoint 2013 dev/test environments in Azure

  Build basic and high-availability SharePoint Server 2013 farms in Azure infrastructure services.

Join the discussion

Contact us	Description
What cloud adoption content do you need?	We are creating content for cloud adoption that spans multiple Microsoft cloud platforms and services. Let us know what you think about our cloud adoption content, or ask for specific content by sending email to cloudadopt@microsoft.com.
Join the cloud adoption discussion	If you are passionate about cloud-based solutions, consider joining the Cloud Adoption Advisory Board (CAAB) to connect with a larger, vibrant community of Microsoft content developers, industry professionals, and customers from around the globe. To join, add yourself as a member of the CAAB (Cloud Adoption Advisory Board) space of the Microsoft Tech Community and send us a quick email at CAAB@microsoft.com. Anyone can read community-related content on the CAAB blog. However, CAAB members get invitations to private webinars that describe new cloud adoption resources and solutions.
Get the art you see here	If you want an editable copy of the art you see in this article, we’ll be glad to send it to you. Email your request, including the URL and title of the art, to cloudadopt@microsoft.com.

Free Step by Step SharePoint Server 2013 Lab Guides by Microsoft

This Post contains a bunch of Free Step by Step SharePoint Server 2013 Lab Guides that Microsoft gives for free on its Download Center. Usually I post them together with the other free resources that Microsoft offers, however this is a Test Lab Guide (TLG) only post, and the rest of the resources will come later in the month.

Microsoft Download Center

1. Test Lab Guide: Configure SharePoint Server 2013 in a three-tier farm
2. Test Lab Guide: Configure intranet and team sites for SharePoint Server 2013
3. Test Lab Guide: Demonstrate permissions with SharePoint Server 2013
4. Test Lab Guide: Demonstrate profile synchronization for SharePoint Server 2013
5. Test Lab Guide: Demonstrate Social Features for SharePoint Server 2013
6. Test Lab Guide: Demonstrate SAML-based Claims Authentication with SharePoint Server 2013
7. Test Lab Guide: Demonstrate forms-based claims authentication for SharePoint Server 2013
8. Test Lab Guide: Configure eDiscovery for SharePoint Server 2013
9. Test Lab Guide: Create a Business Intelligence Baseline Environment
10. Test Lab Guide: Configure Secure Store
11. Test Lab Guide: Configure Excel Services
12. Test Lab Guide: Configure the Excel Services unattended service account
13. Test Lab Guide: Configure Excel Services data refresh by using an embedded connection
14. Test Lab Guide: Configure Excel Services data refresh by using an external connection
15. Test Lab Guide: Configure Visio Services
16. Test Lab Guide: Configure the Visio Services unattended service account
17. Test Lab Guide: Configure Visio Services data refresh using an external connection
18. Test Lab Guide: Configure PerformancePoint Services
19. Test Lab Guide: Configure data access for PerformancePoint Services
20. Test Lab Guide Mini-Module: Configuring a Second SharePoint Server 2013 Farm 
21. Test Lab Guide: Configure a Highly Available SharePoint Server 2013 Search Topology
22. Test Lab Guide: Configure an Integrated Exchange, Lync, and SharePoint Test Lab

A very nice Poster from Microsoft that resumes the above http://www.microsoft.com/en-ca/download/details.aspx?id=39298
Teched North America

1. Configuring Office Web Applications for Microsoft SharePoint 2013 
2. Configuring Social Features in Microsoft SharePoint 2013 
3. Extending the Search Experience in Microsoft SharePoint 2013 
4. Introduction to Web Content Management in Microsoft SharePoint 2013 
5. Designing a Microsoft SharePoint 2013 Site 

Migrate Google G-Suite mailboxes to Office 365

Migrate your IMAP mailboxes to Office 365 gives you an overview of the migration process. Read it first and when you’re familiar with the contents of that article, return to this topic to learn how to migrate mailboxes from G Suite (formerly known as Google Apps) Gmail to Office 365. You must be a global admin in Office 365 to complete IMAP migration steps.

Looking for Windows PowerShell commands? See User PowerShell to perform an IMAP migration to Office 365.

Want to migrate other types of IMAP mailboxes? See Migrate other types of IMAP mailboxes to Office 365 .

Migration from G Suite mailboxes using the Office 365 admin center

You can use the setup wizard in the Office 365 admin center for an IMAP migration. See IMAP migration in the Office 365 admin center for instructions.

IMPORTANT: IMAP migration will only migrate emails, not calendar and contact information. Users can import their own email, contacts, and other mailbox information to Office 365. See Migrate email and contacts to Office 365 for Business to learn how.

Before Office 365 can connect to Gmail or G Suites, all the account owners need to create an app password to access their account. This is because Google considers Outlook to be a less secure app and will not allow a connection to it with a password alone. For instructions, see Prepare your G Suite account for connecting to Outlook and Office 365. You’ll also need to make sure your G Suite users can turn on 2-step verification.

Gmail Migration tasks

The following list contains the migration tasks given in the order in which you should complete them.

Step 1: Verify you own your domain

In this task, you’ll first verify to Office 365 that you own the domain you used for your G Suite accounts.

Notes:

• Another option is to use the your company name.onmicrosoft.com domain that is included with your Office 365 subscription instead of using your own custom domain. In that case, you can just add users as described in Create users in Office 365 and omit this task.
• Most people, however, prefer to use their own domain.

Domain verification is a task you will go through as you setup Office 365. During the setup Office 365 setup wizard provides you with a TXT record you will add at your domain host provider. See Verify your domain in Office 365 for the steps to complete in Office 365 admin center, and choose a domain registrar from the two following options to see how to complete add the TXT record that your DNS host provider.

• Your current DNS host provider is Google.    If you purchased your domain from Google and they are the DNS hosting provider, follow these instructions: Create DNS records when your domain is managed by Google.
• You purchased your domain from another domain registrar.    If you purchased your domain from a different company, we provide instructions for many popular domain hosting providers.

Step 2: Add users to Office 365

You can add your users either one at a time, or several users at a time. When you add users you also add licenses to them. Each user has to have a mailbox on Office 365 before you can migrate email to it. Each user also needs a license that includes an Exchange Online plan to use his or her mailbox.

Important: At this point you have verified that you own the domain and created your G Suite users and mailboxes in Office 365 with your custom domain. Close the wizard at this step. Do not proceed to Set up domain, until your Gmail mailboxes are migrated to Office 365. You’ll finish the setup steps in task 7, Route Gmail directly to Office 365.

Step 3: Create a list of Gmail mailboxes to migrate

For this task, you create a migration file that contains a list of Gmail mailboxes to migrate to Office 365. The easiest way to create the migration file is by using Excel, so we use Excel in these instructions. You can use Excel 2013, Excel 2010, or Excel 2007.

When you create the migration file, you need to know the password of each Gmail mailbox that you want to migrate. We’re assuming you don’t know the user passwords, so you’ll probably need to assign temporary passwords (by resetting the passwords) to all mailboxes during the migration. You must be an administrator in G Suite to reset passwords.

You don’t have to migrate all Gmail mailboxes at once. You can do them in batches at your convenience. You can include up to 50,000 mailboxes (one row for each user) in your migration file. The file can be as large as 10 MB.

1. Sign in to G Suite admin console using your administrator username and password.
2. After you’re signed in, choose Users.

   

3. Select each user to identify each user’s email address. Write down the address.

   

4. Sign in to the Office 365 admin center, and go to Users > Active users. Keep an eye on the User name column. You’ll use this information in a minute. Keep the Office 365 admin center window open, too.

   

5. Start Excel.
6. Use the following screenshot as a template to create the migration file in Excel. Start with the headings in row 1. Make sure they match the picture exactly and don’t contain spaces. The exact heading names are:
   • EmailAddress in cell A1.
   • UserName in cell B1.
   • Password in cell C1.

     

7. Next enter the email address, user name, and password for each mailbox you want to migrate. Enter one mailbox per row.
   • Column A is the email address of the Office 365 mailbox. This is what’s shown in the User name column in Users > Active users in the Office 365 admin center.
   • Column B is the sign-in name for the user’s Gmail mailbox—for example, alberta@contoso.com.
   • Column C is the app password for the user’s Gmail mailbox. Creating the app password is described in Migration from G Suite mailboxes using the Office 365 admin center.

     

8. Save the file as a CSV file type, and then close Excel.

   

Step 4: Connect Office 365 to Gmail

To migrate Gmail mailboxes successfully, Office 365 needs to connect and communicate with Gmail. To do this, Office 365 uses a migration endpoint. Migration endpoint is a technical term that describes the settings that are used to create the connection so you can migrate the mailboxes. You create the migration endpoint in this task.

1. Go to the Exchange admin center.
2. In the EAC, go to Recipients > Migration > More > Migration endpoints.

   

3. Click New to create a new migration endpoint.
4. On the Select the migration endpoint type page, choose IMAP.
5. On the IMAP migration configuration page, set IMAP server to imap.gmail.com and keep the default settings the same.
6. Click Next. The migration service uses the settings to test the connection to Gmail system. If the connection works, the Enter general information page opens.
7. On the Enter general information page, type a Migration endpoint name, for example, Test5-endpoint. Leave the other two boxes blank to use the default values.

   

8. Click New to create the migration endpoint.

Step 5: Create a migration batch and start migrating Gmail mailboxes

You use a migration batch to migrate groups of Gmail mailboxes to Office 365 at the same time. The batch consists of the Gmail mailboxes that you listed in the migration file in the previous task.

Tips:

• It’s a good idea to create a test migration batch with a small number of mailboxes to first test the process.
• Use migration files with the same number of rows, and run the batches at similar times during the day. Then compare the total running time for each test batch. This helps you estimate how long it could take to migrate all your mailboxes, how large each migration batch should be, and how many simultaneous connections to the source email system you should use to balance migration speed and Internet bandwidth.

1. In the Office 365 admin center, navigate to Admin centers > Exchange.

   

2. In the Exchange admin center, go to Recipients > Migration.
3. Click New > Migrate to Exchange Online.

   

4. Choose IMAP migration > Next.
5. On the Select the users page, click Browse to specify the migration file you created. After you select your migration file, Office 365 checks it to make sure:
   • It isn’t empty.
   • It uses comma-separated formatting.
   • It doesn’t contain more than 50,000 rows.
   • It includes the required attributes in the header row.
   • It contains rows with the same number of columns as the header row.

   If any one of these checks fails, you’ll get an error that describes the reason for the failure. If you get an error, you must fix the migration file and resubmit it to create a migration batch.

6. After Office 365 validates the migration file, it displays the number of users listed in the file as the number of Gmail mailboxes to migrate.

   

7. Click Next.
8. On the Set the migration endpoint page, select the migration endpoint that you created in the previous step, and click Next.
9. On the IMAP migration configuration page, accept the default values, and click Next.
10. On the Move configuration page, type the name (no spaces or special characters) of the migration batch in the box—for example, Test5-migration. The default migration batch name that’s displayed is the name of the migration file that you specified. The migration batch name is displayed in the list on the migration dashboard after you create the migration batch.

    You can also enter the names of the folders you want to exclude from migration. For example, Shared, Junk Email, and Deleted. Click Add to add them to the excluded list. You can also use the edit icon to change a folder name and the remove icon to delete the folder name.

    

11. Click Next
12. On the Start the batch page, do the following:
    • Choose Browse to send a copy of the migration reports to other users. By default, migration reports are emailed to you. You can also access the migration reports from the properties page of the migration batch.
    • Choose Automatically start the batch > new. The migration starts immediately with the status Syncing.

      

Note: If the status shows Syncing for a long time, you may be experiencing bandwidth limits set by Google. For more information, see Bandwidth limits.

Verify that the migration worked

• In the Exchange admin center, go to Recipients > Migration. Verify that the batch is displayed in the migration dashboard. If the migration completed successfully, the status is Synced.
• If this task fails, check the associated Mailbox status reports for specific errors, and double-check that your migration file has the correct Office 365 email address in the EmailAddress column.

Verify a successful mailbox migration to Office 365

• Ask your migrated users to complete the following tasks:
  • Go to the Office 365 sign-in page, and sign in with your user name and temporary password.
  • Update your password, and set your time zone. It’s important that you select the correct time zone to make sure your calendar and email settings are correct.
  • When Outlook Web App opens, send an email message to another Office 365 user to verify that you can send email.
  • Choose Outlook, and check that your email messages and folders are all there.

Optional: Reduce email delays

Although this task is optional, doing it can help avoid delays in the receiving email in the new Office 365 mailboxes.

When people outside of your organization send you email, their email systems don’t double-check where to send that email every time. Instead, their systems save the location of your email system based on a setting in your DNS server known as a time-to-live (TTL). If you change the location of your email system before the TTL expires, the sender’s email system tries to send email to the old location before figuring out that the location changed. This can result in a mail delivery delay. One way to avoid this is to lower the TTL that your DNS server gives to servers outside of your organization. This will make the other organizations refresh the location of your email system more often.

Most email systems ask for an update each hour if a short interval such as 3,600 seconds (one hour) is set. We recommend that you set the interval at least this low before you start the email migration. This setting allows all the systems that send you email enough time to process the change. Then, when you make the final switch over to Office 365, you can change the TTL back to a longer interval.

The place to change the TTL setting is on your email system’s mail exchanger record, also called an MX record. This lives in your public facing DNS. If you have more than one MX record, you need to change the value on each record to 3,600 seconds or less.

Don’t worry if you skip this task. It might take longer for email to start showing up in your new Office 365 mailboxes, but it will get there.

If you need some help configuring your DNS settings, see Create DNS records for Office 365 when you manage your DNS records.

Step 6: Update your DNS records to route Gmail directly to Office 365

Email systems use a DNS record called an MX record to figure out where to deliver email. During the email migration process, your MX record was pointing to your Gmail system. Now that you’ve completed your email migration to Office 365, it’s time to point your MX record to Office 365. After you change your MX record following these steps, email sent to users at your custom domain is delivered to Office 365 mailboxes

For many DNS providers, there are specific instructions to change your MX record, see Create DNS records for Office 365 when you manage your DNS records for instructions. If your DNS provider isn’t included, or if you want to get a sense of the general directions, general MX record instructions are provided as well. See Create DNS records at any DNS hosting provider for Office 365 for instructions.

1. Sign in to Office 365 with your work or school account.
2. Go to the Domains page.
3. Select your domain and then choose Fix issues.

   The status shows Fix issues because you stopped the wizard partway through so you could migrate your Gmail email to Office 365 before switching your MX record.

   

4. For each DNS record type that you need to add, choose What do I fix?, and follow the instructions to add the records for Office 365 services.
5. After you’ve added all the records, you’ll see a message that your domain is set up correctly: Contoso.com is set up correctly. No action is required.

It can take up to 72 hours for the email systems of your customers and partners to recognize the changed MX record. Wait at least 72 hours before you proceed to stopping synchronization with Gmail.

Step 7: Stop synchronization with Gmail

During the last task, you updated the MX record for your domain. Now it’s time to verify that all email is being routed to Office 365. After verification, you can delete the migration batch and stop the synchronization between Gmail and Office 365. Before you take this step:

• Make sure that your users are using Office 365 exclusively for email. After you delete the migration batch, email that is sent to Gmail mailboxes isn’t copied to Office 365 This means your users can’t get that email, so make sure that all users are on the new system.
• Let the migration batch run for at least 72 hours before you delete it. This makes the following two things more likely:
  • Your Gmail mailboxes and Office 365 mailboxes have synchronized at least once (they synchronize once a day).
  • The email systems of your customers and partners have recognized the changes to your MX records and are now properly sending email to your Office 365 mailboxes.

When you delete the migration batch, the migration service cleans up any records related to the migration batch and removes it from the migration dashboard.

Delete a migration batch

1. In the Exchange admin center, go to Recipients > Migration.
2. On the migration dashboard, select the batch, and then click Delete.

How do you know this worked?

• In the Exchange admin center, navigate to Recipients > Migration. Verify that the migration batch no longer is listed on the migration dashboard.

Step 8: Users migrate their calendar and contacts

After your migrate their email, users can import their Gmail calendar and contacts to Outlook:

• Import contacts to Outlook
• Import Google Calendar to Outlook