This document introduces Alexis Conia and Eudes Olivier, MVPs for Microsoft Teams and Skype for Business. It discusses why organizations should migrate from Skype for Business to Microsoft Teams, noting Teams' improved features, user experience, and performance. It outlines different migration approaches like side-by-side usage with overlap, introducing Teams without overlapping functionality, or adopting a "Meetings First" strategy. Organizations can choose approaches depending on their current setup and complexity. The document provides resources on Microsoft's guidance for the journey to migrating to Teams.

1. Qui sommes Nous?
Alexis | @alexis_conia
MVP Office App & Services
Microsoft Teams & SfB
Technical Lead
Neitiv
Eudo | @eudesolivier
MVP Office App & Services
Microsoft Teams & SfB
Business Developer UC
Exaprobe

2. Youtube
• https://www.youtube.com/channel/UCwEX6aUYasm7_-BnM6w0QhA

3. Alexis Conia | Eudes Olivier ROBERT
CTO | Business Developer UC
MVP Microsoft Teams
Migration de Skype for Business vers
Microsoft Teams ?

4. Pourquoi migrer vers Teams
et pourquoi c’est important d’y penser dès maintenant
Fonctionnalités
Teams fait déjà mieux que Skype for
Business Online
Une feuille de route rapide,
innovante pour des communications
intelligentes et riches
Experience
utilisateur
Moderne, experience riche
Expériences multi-plateformes et
mobiles à la pointe de la
technologie
Collaboration, Teams et Canaux
Performance
Operationelle
Client modern construit sur une
plateforme performante
Teams apporte des améliorations en
termes de qualité et de métriques
opérationnelles

5. Qu’est ce que la migration?
Pour la faire court…
client SfB meetings uniquement
“Utilisateur Migré” = Utilisateur “Teams Only”
L’histoire
Experience d’un utilisateur Teams Only
Chat & Appels
Recevoir et initier tous les chats et les appels dans Teams
Peut s’interopérer (IM/appels) avec les utilisateurs SfB
Etre rediriger vers Teams quand on se signe sur SfB
Conférences
Planifier toutes les conférences dans Teams
Peut joindre les conferences exitantes dans SfB
Données qui seront migrées
Les contacts existants dans SfB incluant les fédérés
Les conferences existantes on prem

6. Client SfB requis
pour joindre une
conférence SfB
Conférences: on peut toujours utiliser les deux types,
pas d’interoperabilité
Le client de conference doit
être celui du service utilisé
Les Utilisateurs peuvent toujours utiliser
leur client de conférence, qu’ils aient été
migrés ou non
Client Teams
requis pour
joindre une
conférence
Teams
L’utilisateur SfB peut
utiliser le client Teams
pour joindre une
conference organisée par
un utilisateur Teams
l’utilisateur Teams
peut utiliser le client
SfB pour joindre une
conference organisée
par un utilisateur SfB

8. User’s upgrade journey – pure SfB Online org
Full side-by-side approach (with overlap)
Enable Teams with broadest possible functionality
Allow users to experience benefits of Teams digital transformation soonest
Each system operates independently, without interoperability
All users must run both SfB and Teams clients at all times until they become Teams Only

9. Org’s upgrade journey – pure SfB Online org
Full side-by-side approach (with overlap)
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

11. User’s upgrade journey – more complex orgs – no overlap
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, notifications, files, apps…)
Switch UC functionality over to Teams
Non-upgraded users and upgraded users rely on interop to communicate

12. Org’s upgrade journey – more complex org – no overlap
For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality
Variation A: for orgs with no prior Teams usage

13. 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

14. For on on-prem & hybrid orgs, that will move to Meetings First before going Teams Only
Start state: user only has SfB with UC functionality.
Introduce Teams to the user, without UC functionality (as previously described)
Adopt Teams Meetings First: switch Meetings scheduling functionality from SfB to Teams
Up to this point, all calls and chats initiate from and land in SfB, no need for interop yet
At some point in the future, upgrade fully to Teams Only
Chat & Calling between Upgraded (Teams Only) users and all other users relies on interop

15. Org’s upgrade journey – more complex org – Meetings First
For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality

17. Meetings First
Keep running Skype for Business Server for chat
and calling
Address meetings now, Enterprise Voice and Chat
next
Simplified, streamlined meetings centric Teams
experience
Meet in Teams
Provide best, richest, complete meetings
experience
Include meeting rooms, devices, services (Cloud
Video Interoperability)
Enjoy harmonious coexistence
Your Teams and Skype for Business clients play nice
with each other
Your Skype for Business meetings are now Teams
meetings
Full IT story – provisioning, reporting…
Configuration and program to migrate users to Teams meetings first

18. Streamlined for meetings specific deployment and
adoption
Chat and Calling tabs off
Admin may turn Teams & Channels tab off if desired
Full meeting lifecycle experience
New, richer meetings app
Improved pre- and post-meeting experiences
All the benefits of Teams meetings
Meet anywhere
Meet with intelligence
Meet with confidence
Meetings First
New, meetings centric user experience
TEAMS + CHANNEL NOTIFICATIONS
NEW MEETING INVITES
SCHEDULE A MEETING/LIVE-EVENT/MEET-NOW
CALENDAR
MEETINGS
TRIAGE MEETING CHAT
PRE POST MEETING SCENARIOS
FIND LIVE MEETINGS
FIND MEETING RECORDINGS*
Preliminary design subject to change without notice

19. Preliminary design subject to change without notice

20. Journeys to Teams – summary
Pure SfB Online customer (unless complex)  short journey
Side-by-side with overlap (chat, calling, meeting scheduling)
Saturate, then rapid upgrade
Unless not comfortable with two clients doing the same thing
SfB on-prem or hybrid or complex  long journey
Introduce Teams without overlap (i.e. no chat, calling, meeting scheduling)
If possible minimize interop duration
If no EV  work on meetings readiness, upgrade users
If EV  consider starting with Meetings First; then work on calling readiness, upgrade users

21. Ressources Microsoft
• Journey to teams
• PowerPoint https://aka.ms/SE-Upgrade-Deck
• Video 1 https://aka.ms/teams-upgrade-1
• Video 2 https://aka.ms/teams-upgrade-2
• Video 3 https://aka.ms/teams-upgrade-3

22. Merci