4th of March 2017

@MS HQ Munich

Big Scale Migration to Office 365Samuel Zuercher [MVP], Senior Consultant #SPSMUC09

› Senior Consultant

› Co Founder Experts Inside

› SharePoint since 2005

› Founder SharePoint Community Switzerland

› MVP since 2011

› @sharepointszu

› Sharepointszu.com

SAMUEL ZUERCHER [MVP]

It’s not a question if you go to the cloudbut WHEN you go with WHAT

IT’SNOT A QUESTIONANYMORE IF YOU GOTO THE CLOUD BUT WHEN, AND WITHWHAT WORKLOADThis is NOT an alternative Fact

WHAT IS THIS SESSION ABOUT

› The Baseline of big scale

› Planning from CMO to FMO

› Technical aspects, conciderations andpitfalls to avoid

THE BASELINE

WHAT DO I MEAN WITH BIG SCALE

› A Customer based in Switzerland› 60’000 Employees world wide› 47 Countries› 280 Locations› 16’000 Users with a Mailbox› 22 TB of Fileshare Data› 1.2 TB of SharePoint Data

GEOGRAPHICAL SPREAD

AFRICA

ALGERIACAMEROONGUINEAGHANAKENYAMOROCCONIGERIASOUTH AFRICATANZANIA

ASIA & MIDDLE EAST

CHINAISRAELJAPANSAUDIA ARABIAKOREAOMAN

CENT. AMERICA & CARIBBEAN

ARUBACOSTA RICADOMINICAN REPUBLICDUTCH CARIBBEANHONDURASMEXICOTRINIDAD AND TOBAGO

EUROPE

AUSTRIABELGIUMBULGARIACYPRUSDENMARKFINLANDFRANCEGERMANYGREAT BRITAINGREECEIRELANDNETHERLANDSPOLANDPORTUGALROMANIARUSSIASPAINSWITZERLAND

NORTHAMERICA

CANADAUSA

SOUTH AMERICA

ARGENTINABRAZILCHILEECUADORPERUVENEZUELA

CIO VISION:

MOVE EVERYTHINGTO OFFICE 365 WITHIN 12 MONTHS

THE PLAN FROM CMO TO FMO

OVERALL STRATEGY

TRANSFORMATION PHASE

Project start Discovery

Define Design Build & Test

Pilot Migration DecommissioningHandover &

Project closure

THE PROJECT PHASES

PHASE 1 - PREPARATION

1. Discover

2. Define

3. Design

PHASE 1 - DISCOVER

1. Know the Environment you are goingto migrate to Office 365

2. Use existing Documentation – but don’t trust it blindly

3. Find the KNOWLEDGABLE people

4. Create MEANINGFUL surveys

PHASE 1 - DEFINE

1. There are a thousand things to betalked about and defined

2. Not all definitions can be doneupfront, give the Project some time

3. Make sure, Definitions you make areunderstood by you and the Customer

PHASE 1 - DESIGN

1. Create an overall Architecture for theMigration

2. Work with big Pictures

3. Nail down the important baselines for the Migration

4. Make all written, document decisions

PHASE 2 – PILOT PHASE

1. Build & Test

› Build and Test Tenant, Identity and Network

› Build and Test Mail

› Build and Test SharePoint

› Build and Test Fileshare

› Build and Test OneDrive for Business

PHASE 2 – BUILD AND TEST

1. Prepare the Architecture, the Tools and implement the central settings

2. Create a representative Pilot Group with different User types at different geographical locations

3. Take time for Testing and Remediation

PHASE 3 – TRANSITION PHASE

1. Migration

› Migration Types (e.g. User Centric vs. Service Centric)

› Migration batches

› Communication and Training

› Network Bandwith / Transition time

PHASE 3 – MIGRATION

1. Do Pre-Synchronization as much asyou can to have user friction as low aspossible

2. Make sure you do not overroll theUser with too much at one time

3. Communication and Training is key

PHASE 4 - CLOSING

1. Decommissioning

2. Handover to Operations

3. Project Closing

PHASE 4 - DECOMMISSIONING

1. Make sure you design the Migration so that you can decomission easily

2. Not getting rid of On Prem assets will not fully give you the savings youmight expect from Office 365

3. This task is not always very easy

PHASE 4 – HANDOVER TO OPERATIONS

1. Make sure you have gooddocumentation

2. Involve Operations at an early stage, not only when you finish

3. Runbooks should be written byOperations not by the Project

PHASE 4 – PROJECT CLOSURE

1. Handover all Documents to theCustomer (internal or external)

2. Make sure you have signoffs

3. PARTY

TECHNICAL ASPECTS ANDCONCIDERATIONS

TENANT TECH

1. There are numerous settings to lookat on a Tenant level

2. Some basics like «Sharing» and«Security» are very important

3. Loads of possibilites like who cancreate Groups, who can Sync ODFB

TENANT OPS

1. Office 365 pushes new features in monthly

2. «someone» has to cope with this, analyse, make a strategy and work on

3. In big Scenarios, with multi Forest andADFS you have a lot to look after!!

IDENTITY AND AUTHENTICATION

1. ADFS is not anymore the only answerfor large Enterprises

2. Pass Through Authentication (Preview) is SSO capable without heavy Infra.

3. If you do ADFS, make sure you knowwhat you are doing

IF YOU DECIDE TO DO ADFS

1. Make sure you use up to date Servers to run it on

2. Be aware that you have to conciderModern Auth or alternate login ID

3. You should go fully cloud redundant ifpossible

HOW MICROSOFT SHOWS ADFS HA

This looksso simple!!

THISISONLYTHEDR SITE

ADFS PITFALLS

› Only a PLUS for personal, domainjoined Machines / Sessions (i.E. Citrix)

› BYOD needs special Settings on ADFS

› Azure DR Farm needs to be part of On Prem Farm (ADFS Context)

› Multi Forest, same Namespace needsAlternate Login ID and AD DS Trusts

MAIL TECH

1. The preffered method of migratingExchange still is Hybrid

2. Hosted Exchange is NOT hybrid capable

3. Exchange 2010 can now directlyhybrid with Office 365

MAIL TECH 2

1. There are LOADS of possibilities in Office 365 working with your Mailflow, Protection and much more

2. You should closely look at thesesettings and decide on how to use it

3. PST Import for non Exchange

MAIL PITFALLS

1. Access delegated Mailboxes need tobe migrated at the same time

2. Outlook does simple authentication, does not benefit from ADFS

3. Make sure Autodiscover andCertificates are set up correctly

SHAREPOINT TECH

1. Needs firm analysis of customizations

2. Customized pages very often need tobe migrated through content Migration

3. High Speed Migration has loads ofdisadvantages and Online is very slow

4. Use the right tools

SP MIGRATION MATRIX

REALOCATE

REMEDIATE

MIGRATE

YOURS SHAREPOINT SITES

SHAREPOINT PITFALLS

1. Make sure you have all AD Groups andUsers in Azure AD before migrating(especially in multi Forest scenarios)

2. Sites at the same size do not take thesame time when migrating (dependson the number of Objects)

SHAREPOINT PITFALLS 2

1. Depending on the Hostname, youcould still have too long URLs

2. Really no full trust code in the Cloud!!

3. Remediate full trust to Ad-In Model can be very cost and time consuming

› Concider SPCAFF to remediate!!

FILESHARE TECH

1. Fileshare is quite easy to migrate

2. No more blocked files in SP Online

3. 10 GB per File, 25 TB per Site leavesyou without any problem

4. Make sure you have good tooling for Metadata and Security

FILESHARE PITFALLS

1. Make sure you have RemediationProject before Migration

2. You will migrate the same shit for less, if you don’t cleanup

3. To long URL very likely as Users loveputting abstracts to the Filename

FILESHARE PITFALLS 2

1. Security on Fileshares is mostprobably much too complex

2. Fileshares grew historically and arevery likely to be a mess

3. Don’t try to get rid of Folders, more tryto distinct between Consumer andContributor Views (Folders, Metadata)

SKYPE FB TECH

1. If you only use Cloud Skype FB it isreally easy and reliable

2. It is much more complex if you wantto use PBX integration

3. Cloud PBX is in the come, concider thisif you plan!

SKYPE FB PITFALLS

1. Be aware that Skype Video generatesmuch Network Traffic

2. Not concidering Network whendeploying can interupt your Ops

3. Be aware of Versions if you have i.E.Citrix in place

ODFB TECH

1. OneDrive for Business is actually thesimplest to deploy and Migrate

2. You always have 1:1 relationship andyou don’t have to care about security

3. Be aware, ODFB Sync Client Deploy-ment can be tricky (Groove.exe vs. Next Gen Sync Client etc.)

ODFB PITFALLS

1. Offline Sync can kill your Network, ifall Users do it at the same time

2. Local Disks can overflow if Users try tosync a whole very big Library

3. URL length most likely to be too longwhen migrating (proper Tooling!!)

NON TECH PITFALLS

1. Do not underestimate the Complexity, even if it is «all easy Office 365»

2. Many, Geographically spread branchesis highly complex and needs planning

3. Take IT affinity into Concideration

4. Maturity of Company IT is key

HUMAN FRICTION

1. You will need a good and strong team

2. If you have non-teamplayers in theteam get rid of them

3. If you have low knowledge (selfoverrating) people on the team, get ridof them

4. Make sure your PMs are MASTERS

Thank you!