Home

Teams-SfB Forced Migration Pains

%3CLINGO-SUB%20id%3D%22lingo-sub-794609%22%20slang%3D%22en-US%22%3ETeams-SfB%20Forced%20Migration%20Pains%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-794609%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20a%20smaller%2020-50%20user%20ICT%20service%20organisation%20and%20were%20forced%20to%20migrate%20to%20Teams%20from%20SfB%20in%20our%20Office%20365%20Business%20Premium%20subscription.%3CBR%20%2F%3EMany%20of%20our%20customers%20are%20large%20enterprise%20organisations%20who%20are%20still%20on%20SfB%20(and%20still%20have%20a%202%20year%20grace%20period)%20in%20the%20Microsoft%20cloud.%26nbsp%3B%3CBR%20%2F%3EWhile%20we%20were%20still%20on%20SfB%20we%20could%20easily%20do%20a%20lot%20of%20stuff%20with%20SfB%20users%20from%20our%20customers%20that%20are%20no%20longer%20available%20with%20Teams%3A%3CBR%20%2F%3E-%20Share%20Desktop%3C%2FP%3E%3CP%3E-%20Paste%20images%20and%2For%20documents%20into%20a%20chat%20(Now%20we%20can%20do%20text%20only%20chats%20only%20-%20Back%20to%20the%20mainframe%20era%20%3F)%3C%2FP%3E%3CP%3E-%20Do%20meetings%20(we%20need%20to%20launch%20a%20separate%20SfB%20web%20meetings%20app%20to%20do%20that)%3C%2FP%3E%3CP%3Eand%20some%20other%20less%20inconveniences%E2%80%A6%3CBR%20%2F%3E%3CBR%20%2F%3EIMHO%20a%20forced%20migration%20to%20Teams%20for%20smaller%20tenants%20is%20a%20complete%20wrong%20strategy%20as%20Teams%20obviously%20still%20isn't%20ready%20while%20it%20is%20still%20missing%20basic%20features%20like%20the%20ones%20mentioned%20above.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20deactivate%20this%20forced%20migration%20and%20go%20back%20to%20our%20beloved%20SfB%20(which%20also%20had%20some%20shortcomings%20of%20course)%20which%20provided%20us%20teh%20means%20to%20get%20our%20work%20done%20more%20effectively%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPeter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-794609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-795548%22%20slang%3D%22en-US%22%3ERe%3A%20Teams-SfB%20Forced%20Migration%20Pains%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-795548%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389043%22%20target%3D%22_blank%22%3E%40PeHobe%3C%2FA%3E%26nbsp%3BI%20don't%20see%20any%20way%20of%20going%20back%20to%20Skype.%20I%20just%20tried%20setting%20the%20tenant%20upgrade%20policy%20and%20user%20upgrade%20policy%20to%20%22islands%22%20or%20%22sfbonly%22%20via%20PowerShell%2C%20but%20it's%20not%20possible%20anymore.%20I%20had%20the%20slight%20hope%20that%20it%20would%20be%20still%20possible%20there%2C%20but%20nope.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%26gt%3B%20Grant-CsTeamsUpgradePolicy%20-Global%20-PolicyName%20tag%3Aislands%3CBR%20%2F%3ETeamsUpgradePolicy%20cannot%20be%20set%20because%20Microsoft%20has%20already%20upgraded%20this%20organization.%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-795688%22%20slang%3D%22en-US%22%3ERe%3A%20Teams-SfB%20Forced%20Migration%20Pains%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-795688%22%20slang%3D%22en-US%22%3EDon't%20know%20about%20the%20screenshot%20stuff%2C%20but%20screen%20sharing%20from%20Teams%20to%20Skype%20is%20coming%20see%20road-map%20item%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Frtc%3D2%26amp%3Bfilters%3D%26amp%3Bsearchterms%3D53934%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Frtc%3D2%26amp%3Bfilters%3D%26amp%3Bsearchterms%3D53934%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20meetings%20thing%20isn't%20a%20big%20deal%2C%20once%20they%20move%20to%20Teams%20that%20issue%20will%20go%20away.%20No%20different%20than%20having%20to%20join%20another%20companies%20Zoom%20or%20webex%20meeting.%20%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20for%20being%20able%20to%20roll%20back%20that's%20not%20possible%20any%20longer.%20I%20agree%20the%20whole%20screen%20sharing%20should%20have%20been%20released%20along%20with%20a%20couple%20other%20things%20before%20forcing%20people%20to%20switch%20%3A).%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
PeHobe
Occasional Visitor

We are a smaller 20-50 user ICT service organisation and were forced to migrate to Teams from SfB in our Office 365 Business Premium subscription.
Many of our customers are large enterprise organisations who are still on SfB (and still have a 2 year grace period) in the Microsoft cloud. 
While we were still on SfB we could easily do a lot of stuff with SfB users from our customers that are no longer available with Teams:
- Share Desktop

- Paste images and/or documents into a chat (Now we can do text only chats only - Back to the mainframe era ?)

- Do meetings (we need to launch a separate SfB web meetings app to do that)

and some other less inconveniences…

IMHO a forced migration to Teams for smaller tenants is a complete wrong strategy as Teams obviously still isn't ready while it is still missing basic features like the ones mentioned above.

 

Is there a way to deactivate this forced migration and go back to our beloved SfB (which also had some shortcomings of course) which provided us teh means to get our work done more effectively?

 

Peter

2 Replies

@PeHobe I don't see any way of going back to Skype. I just tried setting the tenant upgrade policy and user upgrade policy to "islands" or "sfbonly" via PowerShell, but it's not possible anymore. I had the slight hope that it would be still possible there, but nope.

 

> Grant-CsTeamsUpgradePolicy -Global -PolicyName tag:islands
TeamsUpgradePolicy cannot be set because Microsoft has already upgraded this organization.

 

Don't know about the screenshot stuff, but screen sharing from Teams to Skype is coming see road-map item: https://www.microsoft.com/en-us/microsoft-365/roadmap?rtc=2&filters=&searchterms=53934

The meetings thing isn't a big deal, once they move to Teams that issue will go away. No different than having to join another companies Zoom or webex meeting.

As for being able to roll back that's not possible any longer. I agree the whole screen sharing should have been released along with a couple other things before forcing people to switch :).

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
202 Replies