1. Tom Lewis, Director Academic & Collaborative Applications UW Information Technology The Saga of UW’s Office365 Implementation

2. July – August 2011 Foolish Optimism o Live@edu migration/general availability O365 project kickoff meeting Project end date of November 2011 o Equipment needs identified and orders placed o Decision to use F5 load balancers – new project spun up o Asked Microsoft for permanent test tenant Senior UW-IT leadership emails senior Microsoft leadership about delay and lack of response to our request 2

3. September – October 2011 Uh-oh o All equipment delivered and built out o Dogfood tenant finally provisioned by Microsoft A month after UW-IT leadership email Not a true EDU tenant or XL size o Slippage of timeline o Start to realize how horrible the transition will be for Live@edu users 3

4. November – December 2011 Eyes Opening Widely o Deep dive with Microsoft on O365 and UW environment o Contracting with Microsoft Premier Deployment team o More discovery on how bad the migration for Live@edu users o First taste of how poor Microsoft’s support of O365 versus Live@edu o TAP & MSO based Strawman for migration 4

5. January – February 2012 Holding…. o Engaged with Microsoft on deep dive for TAP o Standard non-EDU and XL tenant fiasco o UW Medicine decides they want to move to O365 5

6. March - May 2012: Holding… o In-place conversion versus “greenfield” approach o Decision to go with “greenfield” approach o Problems with DirSync limitations o Confirmed with Microsoft a migration path for Live@edu users o Move away from FIM and go back to DirSync 6

7. June – August 2012 More Holding… o Contract should be signed and ready to go by July 1st o Strawman for migrating Live@edu users finalized o Ask Microsoft if we can keep old Live@edu tenant and upgrade it to O365 o Microsoft responds two months later that they can upgrade our existing Live@edu tenant 7

8. September – December 2012 1 of Many Stages of Grief o Microsoft does bait and switch on contract o Live@edu upgrade to Office 365 finally happens o Major outage of Live@edu o Contract and licensing for O365 finalized (signed) o Talks with Microsoft to confirm we have proper support for O365 o Changed the mail attribute value to @uw.edu 8

9. January – April 2013 Grief Diminishes o Changed primary SMTP for mail enabled users o Followed the Google groups method of email address of @uw.edu for Exchange enabled groups o Mega GAL testing o Decided to scrap everything with WAVE 14 and go to WAVE 15 o Microsoft provisions WAVE 15 tenants 9

10. May – August 2013 Change of Direction o Decision to install Exchange 2013 for mailbox migrations o Setup DirSync in Dogfood environment (Wave 15) o Decided to deliver SkyDrive Pro (now One Drive for Business) and Lync Online to campus before Exchange Online o Decided to migrate Exchange Local users to Exchange Online before general availability (manual process) o Receive quote from Microsoft for Exchange Online migration (~$1,000,000) o Production SkyDrive Pro and Lync Online environment setup o Early adopters given accounts (~1000) 10

11. September – December 2013 Progress Finally Contract with Cloudbearing to help with Live@edu migrations established SkyDrive Pro and Lync Online released to campus (~140,000 accounts provisioned) Lowered UW Exchange Local message size limit from 60 MB to 25 MB (to match Exchange Online) Production Exchange Online (hybrid) successfully setup First UW Exchange Local mailbox successfully migrated to Exchange Online 11

12. January – April 2014 Towards a Happy Ending? o Large mail message report sent out to UW Exchange Local support groups o Exchange Online pilot begins (migrated a couple hundred selected users) o Mass migrations from UW Exchange Local to Exchange Online begins o ~2400 migrated as of today 12

13. Lessons Learned Vendor Management o Microsoft O365 technologies and support are not mature, so continual engagement required Teams still working at cross purposes o Ask not, do Many things are not so enterprise with licensing and otherwise Beware the HIPAA-busting updates o Verify and then trust with Microsoft and their partners o NET+ helps 13

14. Lessons Learned Campus Change Management o Email costs will not diminish for awhile (if ever) Will still need lots of hardware too o Communicate the timelines, communicate the details Lots of community meetings Public product backlog Talk up the value o Work closely in pilot mode with department IT, early adopters o Pilot early, and pilot for a loooooong time Create a public and open communication channel 14

15. Lessons Learned Policy Implications o Account life-cycle management comes to the fore Whither Alumni? Separation business processes often Lots of community meetings Public product backlog o HIPAA means lots of discussion on e-discovery o Engage early and often with your counsel I am not a lawyer, but I play one at work… 15