11/8/2018 1:42 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.

Upgrading to Teams BJ Whalen Francois Doremieux BRK3142
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

The Skype to Teams quartet at Ignite
There are four Ignite sessions focusing on the upgrade experience Designing your path from Skype for Business to Teams: <Start Here> Planning the end-to-end upgrade experience BRK3141 Planning a seamless migration from Skype for Business to Teams for IT Admins BRK3142 Delighting your End Users: Facilitating a smooth transition from Skype for Business to Teams BRK2190 “Meetings First” Microsoft Teams Meetings for Skype for Business Server users BRK3124 PLUS Come learn how Microsoft is managing the upgrade to Teams BRK3230: How Microsoft Does IT: The Journey from SfB to Teams © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

What to expect from today’s session
11/8/2018 1:42 AM What to expect from today’s session Objectives Key Takeaways Understand the end user experiences when both SfB (online/hybrid/onprem) and Teams are present in an org Understand how to manage co-existence of SfB and Teams in an org Explain the recommended migration path to achieve a smooth transition to Teams Microsoft is providing tools for you to manage your E2E migration Whether coming from on-prem or online, there is a simple path to get from SfB to Teams You can customize the deployment path to fit your needs © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Agenda Recommended upgrade path for pure SfBO orgs
Tech Ready 15 11/8/2018 Agenda Recommended upgrade path for pure SfBO orgs The Teams-only experience Upgrade paths for other orgs Typical Migration Paths Interop between SfB and Teams Managing Coexistence Planning your migration Q&A © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Why should you migrate to Teams
Why you should actively consider it now Features and capabilities Teams can already do more than Skype for Business Online Rich Intelligent Communications roadmap and rapid innovation User experiences Modern, rich experiences State-of-the-art cross-platform and mobile experiences Collaboration, Teams and Channels Operational performance Modern client built on modern infrastructure Teams can provide improvements in quality and operational metrics © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Flexibility based on a proven framework
End-to-end process enabling customers to plan, coexist, prepare users and upgrade when ready Project Stakeholders Project Definition Technical Readiness and User Readiness Deployment and Implementation Operational Excellence + Gather the right sponsors and project team Drive value with sustained operations and user adoption Define your project scope, goals and timeline Implement pilot, coexist and upgrade strategy Assess network readiness; test for quality Assess user acceptance and design readiness plan © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrade Objectives Enable SfB Online users to move to Teams
Enable SfB on-prem users to move to Teams Provide interop between users who have SfB and those with Teams Empower admins to selectively move users Note: The terms “upgrade” and “migration” are used interchangeably in this deck © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrading from pure SfB Online
11/8/2018 1:42 AM Upgrading from pure SfB Online © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Pure SfB Online Organization: User perspective
11/8/2018 1:42 AM Pure SfB Online Organization: User perspective Full Side by Side Approach + Enable Teams with full functionality Allow users to experience full benefits of Teams digital transformation soonest All users must run both SfB and Teams clients at all times until they become Teams Only © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Pure SfB Online Organization: Org perspective
Full side-by-side approach Teams (Drive saturation while SfBO still on) SFBO Teams & SFBO Side by side Teams Only Deploy Teams side-by-side with SfB Online with full functionality in Teams Drive rapid adoption across your organization to saturation, while leaving SfB enabled. Once you have reached a saturated level of adoption and all room devices are deemed Teams compatible, upgrade all users to Teams-only as rapidly as possible.

Demo: Full side by side experience
11/8/2018 1:42 AM Demo: Full side by side experience © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

The Teams-Only Experience

Long Story: Experience of a Teams-Only user
What is Upgrade? Long Story: Experience of a Teams-Only user Short Story: = “Upgraded User” “Teams-Only User” Chat & Calling Receives and initiates all chats and calls in Teams Can interop (IM/call) with any SfB user Is redirected to Teams if they try to sign in to SfB Meetings Schedules all new meetings in Teams Can join existing SfB Meetings Data that gets migrated Existing contacts from SfB Existing on-prem meetings © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Demo: Teams-Only end user experience
Francois Doremieux © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrade for more complex orgs
11/8/2018 1:42 AM Upgrade for more complex orgs © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/8/2018 1:42 AM Upgrade from a user’s point of view For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality + Starting point: User is in SfB with UC functionality Introduce Teams to the user, without UC functionality All calls & chat continue to land in and originate from SfB User can explore net new functionality of Teams (Channels/apps/etc) Switch UC functionality over to Teams Non-upgraded users and upgraded users rely on interop to communicate © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Demo: Teams without UC functionality
Francois Doremieux © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Org perspective: Upgrade without overlapping functionality
11/8/2018 1:42 AM Org perspective: Upgrade without overlapping functionality For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality Variation A: No prior Teams usage Original User Population Pilot expands Begin Teams Pilot Migration Complete SFB SFB With Teams (no UC) Teams During migration, users in SfB can communicate with users in Teams via interop Presence is aligned with routing SfB users can use non-UC functionality in Teams prior to upgrade © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Org perspective: Upgrade without overlapping functionality
11/8/2018 1:42 AM Org perspective: Upgrade without overlapping functionality For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality Variation B: For orgs with prior Teams usage Original User Population Pilot expands Begin Teams Pilot Migration Complete SFB With Teams (no UC) SFB Teams SFB and Teams © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/8/2018 1:42 AM Upgrade from a user’s point of view: Meetings First For on on-prem & hybrid orgs, that will move to Meetings First before going Teams Only More details: BRK3124 Friday 11:30am + + Begin State: User is in SfB with UC functionality. Introduce Teams to the user, without UC functionality, previously described Switch Meetings scheduling functionality from SfB to Teams Up to this point, all calls and chats initiate from and land in SfB Upgrade fully to Teams-Only Teams Chat & Calling between Upgraded (Teams-Only) users and all other users relies on interop © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/8/2018 1:42 AM Meetings scenarios Meeting client must match the service that hosts the meeting Users can always use either meeting client, whether upgraded or not SfB client required to join SfB meeting Teams client required to join Teams meeting SfB user can always use a Teams client to join a meeting organized by a Teams user Teams user can always use an SfB client to join a meeting organized by an SfB user © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Interop 101 What is Interop? Why is Interop Needed?
11/8/2018 1:42 AM Interop 101 Q Q What is Interop? Why is Interop Needed? A Communication between an SfB user and a Teams user A Teams-Only users must always be able to communicate with SfB users Intra-org during migration Cross-org scenarios during and after migration Chat & Calling 1-on-1 only Plain text chat only Capabilities are identical in federated and in-tenant cases Q Are there Interop Pre-requisites? Advanced features (Partially available today) Creating a meeting provides full featured experience for all users Group chat/group call achieved via auto-invite meeting escalation File/screen sharing achieved via auto-invite meeting escalation Availability: SfB to Teams auto-invite available now Teams to SfB TBD A SfB hybrid topology required Teams-user must be homed in SfB Online to enable 1-on-1 chats & calls Teams users with SfB homed on-premises do not have interop nor ability to federate via Teams © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Demo: Interop Francois Doremieux 11/8/2018 1:42 AM

Managing Coexistence 11/8/2018 1:42 AM

Managing Co-existence
Customers manage interop & coexistence via “mode” Exposed in Teams Admin Center UX and PowerShell Mode governs: Routing of incoming messages and calls In what client do you initiate chat and calls (requires upcoming TeamsAppPermissionsPolicy) In what service do you schedule meetings? Mode is a per user assignment, achieved using O365 admin tools Can also be assigned to on-prem users (except TeamsOnly) If necessary, can mix and match modes across an org

Co-existence Modes Mode Calls and Chats Meeting Scheduling Teams Channels available? Recommended Use Case Teams Only (Requires home in SfB Online) Teams Yes The final state of being upgraded. Will also be default state for *new* tenants (<500 users) as of 10/1/2018 SfB With Teams Collab And Meetings* SfB “Meetings First” scenario: Enables on-prem customers to benefit from Teams meeting functionality, if not yet ready to move calling to the cloud. SfB With Teams Collab* Recommended starting point for on-prem/hybrid orgs. Also for online orgs that want tighter admin control Calls and chats always routed to only 1 client throughout the migration. SfB Only* No Specialized scenario for orgs with strict requirements (e.g. for data control) Islands Either Recommended for online orgs that can migrate fast Allows a single user to evaluate both clients side by side. Chats and calls can land in either client; Users must continue to run both clients. *Aspects of some modes are not yet fully implemented. ETA for preview is Q4 2018

What is Upgrade? Redux The mechanics
11/8/2018 1:42 AM What is Upgrade? Redux The mechanics Upgrade = Assign TeamsUpgradePolicy with “TeamsOnly” mode User must already be in SfB Online What changes when Teams-Only Mode is assigned? Routing of all calls and chats to this user will be to Teams, regardless of sender SfB Client restricts itself to enable meetings-only Meeting scheduling switches to Teams Teams add-in enabled SfB add-in disabled User’s Teams presence is made available to SfB Users Contact migration triggered at next Teams logon Outlook People cards invoke Teams functionality for IM/Calling/Presence HID preferences for inputs on audio devices updated © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Data Migration Contacts Meetings
Contacts are copied from SfB Online in 2 phases After first logon to Teams, contacts are copied to Teams At next Teams logon after user is Teams-only, contacts are copied to Teams and merged with existing contacts Implications for users homed in SfB on-prem: Contacts are moved to SfB Online as part of Move-CsUser, and then above logic is relied upon No SfB contacts available in Teams until user is Teams-Only Meetings If Upgrading from SfB Online: Meetings are not migrated If Upgrading from SfB On-prem: Meetings *are* migrated

Considerations for SfB on-prem orgs
Enabling SfB Hybrid is required to start moving to TeamsOnly All msRTCSIP attributes from on-prem must be sync’d to Azure AD Background: Users with SfB On-prem may use Teams, but: They cannot be “TeamsOnly” (Enforced via grant-CsTeamsUpgradePolicy) They have no interop, no federation from their Teams client (must use SfB client for this) On-prem users must first be moved to online using Move-CsUser, in order to execute grant-csTeamsUpgradePolicy 2-step vs 1-step migration 1 step: use –MoveToTeams switch in Move-CsUser (Requires Server 2019 and CU8 for 2015) 2 steps: use any version of Move-CsUser, then assign TeamsUpgradePolicy mode=TeamsOnly Results are same either way, except Meeting Migration 1-step migration: mtgs will be moved direct to Teams (upcoming functionality) 2-step migration: meetings moved to SfB Online

Demo: Moving a user from SfB on-premises to Teams
BJ Whalen © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Planning your migration
11/8/2018 1:42 AM Planning your migration © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrade Tracks Two options for upgrading: Key difference:
11/8/2018 1:42 AM Upgrade Tracks Two options for upgrading: IT Admin-driven track (You manage it) Microsoft-driven automated upgrades (MS does it for you) Key difference: *How* the migration is initiated What is common: The end user experience of being upgraded The underlying core mechanics © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

IT Admin-driven track Target customers:
11/8/2018 1:42 AM IT Admin-driven track Target customers: Larger online orgs, with dedicated SfB admin Orgs with any on-premises SfB users IT Admin initiates upgrade using tools in Teams Admin Center or PowerShell Available to any organization IT admin can selectively upgrade users at a pace that works for them Can downgrade at any time, if not yet upgraded via MS-assisted track © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Microsoft-driven automated upgrades
11/8/2018 1:42 AM Microsoft-driven automated upgrades Intended for customers with limited IT resources Exclusively for pure-online orgs MS automatically upgrades an entire O365 tenant Advance notice (typically days) given via Message Center, & Admin UI, with subsequent periodic reminders Admin can defer once prior to upgrade When upgrade occurs, the entire tenant is upgraded at once Prior to upgrade date, the org can use features of Admin driven track to self-migrate Org must be deemed eligible for migration, based on SfB feature usage Upgraded org can be reverted by MS only © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Summary of Tracks Area IT Admin Driven
11/8/2018 1:42 AM Summary of Tracks Area IT Admin Driven Microsoft-driven automated upgrades Target customers Larger pure online orgs Hybrid and on-premises orgs Smaller pure online orgs Limited IT resources Scope of upgrade Per user or per tenant Per Tenant* Initiated by IT Admin MS Eligibility Any org Based on SfB feature usage and Teams feature availability Ability to downgrade Yes Customer: Yes, prior to MS upgrade MS: Yes, if needed *Prior to upgrade date, the org can use features of Admin driven track to self migrate on a per user basis. When Microsoft upgrades the tenant, the entire tenant is upgraded at once. © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype-to-Teams Upgrade Planning Resources
Tech Ready 15 11/8/2018 Skype-to-Teams Upgrade Planning Resources High-Level Guidance Technical Concepts © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Please evaluate this session Your feedback is important to us!
11/8/2018 1:42 AM Please evaluate this session Your feedback is important to us! Please evaluate this session through MyEvaluations on the mobile app or website. Download the app: Go to the website: © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

APPENDIX

Basic deployment strategy
11/8/2018 1:42 AM Basic deployment strategy For org that hasn’t started using Teams Immediately set the entire Tenant to SfBWithTeamsCollab Progressively move users to Teams Only mode Users in SfBWithTeamsCollab and TeamsOnly modes have predictable routing with each other Users in SfBWithTeamsCollab can start using Teams Channels at any time Original User Population Migration Complete Begin Teams Pilot Pilot expands SfB With Teams Collab Teams Only © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

What if you already have some users in Islands?
11/8/2018 1:42 AM What if you already have some users in Islands? “Grandfather” existing active Teams users before setting default tenant mode Identify active Teams users via O365 Admin Reporting tools Assign these users an Islands mode policy Then execute basic deployment strategy Set the entire Tenant to SfBWithTeamsCollab Progressively move users to Teams Only mode Users in any SfB* mode and TeamsOnly mode have predictable routing with each other Users in Islands do not have predictable routing when communicating with users in any other modes Original User Population Pilot expands Begin Teams Pilot Migration Complete Islands Mode SfB With Teams Collab Teams Only Active Teams Users Islands Mode © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrading from SfB Online: High level flow
No SfB Hybrid Voice involved Phase Admin steps Configure TeamsUpgradePolicy for migration Grandfather existing active Teams users into Islands mode Set tenant-wide policy to mode=SfBwithTeamsCollab Assign licenses and set policy Adjust Teams related policies as desired In O365, assign Teams license, if not already assigned Notification phase Assign upgrade policy with NotifySfbUsers=true and mode=SfBwithTeamsCollab Grant-CsTeamsUpgradePolicy -PolicyName SfBWithTeamsCollabWithNotify -Identity $user Upgrade Grant-CsTeamsUpgradePolicy –PolicyName UpgradeToTeams –Identity $user

Upgrading from SfB Online: High level flow
With SfB Hybrid Voice (either CCE or OPCH) Phase Admin steps One-time global config Pair the SBC and Teams PSTN edge Create online voice routing policy Optional: Create online dial plans Configure TeamsUpgradePolicy for migration Grandfather existing active Teams users into Islands mode Set tenant-wide policy to mode=SfBwithTeamsCollab Prepare users for voice migration In O365, assign voice routing policy for the users to be migrated and optionally any dial-plans: Outgoing calls will egress via Direct Routing. Media will always flow to the cloud. To keep media local, do this step together with configuring SBC later Assign licenses and set policy Adjust Teams related policies as desired In O365, assign Teams license, if not already assigned Notification phase Assign upgrade policy with NotifySfbUsers=true and mode=SfBwithTeamsCollab Grant-CsTeamsUpgradePolicy -PolicyName SfBWithTeamsCollabWithNotify -Identity $user Upgrade In O365: Grant-CsTeamsUpgradePolicy –PolicyName UpgradeToTeams –Identity $user On SBC: Configure voice routing to enable incoming calls (start sending calls to Direct Routing instead of routing them to Mediation Server)

Upgrading from on-prem: High level flow
No Enterprise Voice configured Phase Admin Steps One-time global config Configure SfB hybrid, if not already done Configure TeamsUpgradePolicy for migration Grandfather existing active Teams users into Islands mode Set tenant-wide policy to mode=SfBwithTeamsCollab Assign licenses and set policy Adjust Teams Policies as required for org In O365, assign Teams license, if not already assigned Notification phase Optional: In on-prem, grant TeamsUpgradePolicy (w/ NotifySfBUsers=true) to pilot users Upgrade In on-prem, run Move-CsUser with -MoveToTeams switch

Upgrading from on-prem: High level flow
With Enterprise Voice configured Phase Admin Steps One-time global config Configure SfB hybrid, if not already done Pair the SBC and Teams PSTN edge Create online voice routing policy/Export voice routes from onprem voice policy Create online dial plans/Export dial plans from on premises Configure TeamsUpgradePolicy for migration Grandfather existing active Teams users into Islands mode Set tenant-wide policy to mode=SfBwithTeamsCollab Assign licenses and set policy Adjust Teams Policies as required for org In O365, assign Teams license, if not already assigned Notification phase Optional: In on-prem, grant TeamsUpgradePolicy (w/ NotifySfBUsers=true) to pilot users Upgrade In on-prem: run Move-CsUser with MoveToTeams switch On SBC: Configure voice routing to enable incoming calls (start sending calls to Direct Routing instead of routing them to Mediation Server) In O365 (after 4 hours): Enable Outgoing calls: Assign voice routing policy to migrated users and optionally any dial-plans

Direct Migration Path to Teams
Starting Point Migration Phase End State Pure SfB T SfB UC User C User D Teams Disabled User A User B During Migration UC Collab T SfB User B User C User A User D Disabled UC UC Collab Teams Only T SfB User C User D User B User A SfB T SfB client with all modalities enabled SfB client disabled (except to join SfB meetings) Teams client with all modalities enabled Legend © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Migration Path with Collab Mode
11/8/2018 1:42 AM Migration Path with Collab Mode Starting Point Migration Phase End State Pure SfB T SfB UC User C User D Teams Disabled User A User B Group Collab Collab Only T SfB User B User C User A User D UC During Migration UC Collab T SfB User B User C User A User D Collab Only UC SfB T SfB client with all modalities enabled SfB client disabled (except to join SfB meetings) Teams client with all modalities enabled Teams client with Group Collab only. No UC Legend © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Availability of Modes Teams-Only and Islands modes are done and available now Other modes can be used now in limited form: Routing and Meeting Scheduling are honored for all modes Teams end user experience is pending delivery of TeamsAppPermissionPolicy Admin configurability: Via PowerShell now Will be exposed in Admin UX once end user experience lands Full support for most modes expected in Q4 Mode Power Shell Admin UX Teams End User UX conforms to desired experience Overall Status ETA for full availability TeamsOnly Y Fully available Now Islands SfBOnly N Partially avail Preview Q4 2018 SfB with Teams Collab N (workaround exists now) SfB with Teams Collab and Meetings Preview Q (see BRK3124)

11/8/2018 1:42 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.

Similar presentations

Presentation on theme: "11/8/2018 1:42 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

11/8/2018 1:42 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.

Similar presentations

Presentation on theme: "11/8/2018 1:42 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN."— Presentation transcript:

Similar presentations

About project

Feedback