Forum Discussion
Solved
Advice needed on how to jury rig Teams
Hi Everyone This is going to be a bit of an...odd request for advice but hear me out there are good (or at least dumb political) reasons I'm asking questions. TLDR version: what's the absolute m...
- For sure. If you ask many Microsoft pro's exchange is the bedrock service of Office/Microsoft 365 and is typically implemented first. Teams - being a native cloud app based in Azure, is architected on Office 365 Groups, Exchange, SharePoint and OneDrive. In order to get the best Teams experience these others should be lit up.
It's great to hear the potential of a POC and an evaluation: having users sign up one at a time into different tenants sounds horrendous and I imagine a great deal of time is spent dealing with this and maintaining this alongside Google, Adobe and probably quite a bit of shadow IT which has crept up. Much of this can be avoided. It's not even to do with products to be honest, its about functionality and productivity. Google doesn't provide it. If you wanted to go with something like Teams in that context it would be Slack which is more cost, then you have to transition to a new voice and calling solution to replace Adobe - probably Cisco, or Bluejeans - trying to integrate and manage that is a massive strain when the alternative already exists and most organisation are moving to 365 exactly for these reasons. Google may work from a limited narrow perspective, but the needs of the organisation are what typically push it to 365 as it has Teams, Stream, Forms, PowerApps, Power BI, and much more: all of this can be controlled from an enterprise perspective with Intune or SCCM. If your users are using Windows for the main, obviously 365 is designed to work natively with the OS.
I could evangelise all day - however, I think you already know hence reaching out here. The community can and will support you on this so keep in touch and I hope it goes well.
Best, Chris
Thanks ChrisHoardMVP
This was more wishful thinking on my behalf considering that someone had bashed Office 365 until it worked without actually implementing exchange (if you try and open outlook online it just crashes out). At the moment we're not tenanted (I think that's the right term) so users have to sign up one at a time. I'm hoping this means we can put together a proof of concept exchange instance without ruffling too many feathers so we can do an evaluation.
Considering how entrenched managers who have control over comms are with regards to staying with G Suite I may have to shelve this idea but not without a fight.
For sure. If you ask many Microsoft pro's exchange is the bedrock service of Office/Microsoft 365 and is typically implemented first. Teams - being a native cloud app based in Azure, is architected on Office 365 Groups, Exchange, SharePoint and OneDrive. In order to get the best Teams experience these others should be lit up.
It's great to hear the potential of a POC and an evaluation: having users sign up one at a time into different tenants sounds horrendous and I imagine a great deal of time is spent dealing with this and maintaining this alongside Google, Adobe and probably quite a bit of shadow IT which has crept up. Much of this can be avoided. It's not even to do with products to be honest, its about functionality and productivity. Google doesn't provide it. If you wanted to go with something like Teams in that context it would be Slack which is more cost, then you have to transition to a new voice and calling solution to replace Adobe - probably Cisco, or Bluejeans - trying to integrate and manage that is a massive strain when the alternative already exists and most organisation are moving to 365 exactly for these reasons. Google may work from a limited narrow perspective, but the needs of the organisation are what typically push it to 365 as it has Teams, Stream, Forms, PowerApps, Power BI, and much more: all of this can be controlled from an enterprise perspective with Intune or SCCM. If your users are using Windows for the main, obviously 365 is designed to work natively with the OS.
I could evangelise all day - however, I think you already know hence reaching out here. The community can and will support you on this so keep in touch and I hope it goes well.
Best, Chris
It's great to hear the potential of a POC and an evaluation: having users sign up one at a time into different tenants sounds horrendous and I imagine a great deal of time is spent dealing with this and maintaining this alongside Google, Adobe and probably quite a bit of shadow IT which has crept up. Much of this can be avoided. It's not even to do with products to be honest, its about functionality and productivity. Google doesn't provide it. If you wanted to go with something like Teams in that context it would be Slack which is more cost, then you have to transition to a new voice and calling solution to replace Adobe - probably Cisco, or Bluejeans - trying to integrate and manage that is a massive strain when the alternative already exists and most organisation are moving to 365 exactly for these reasons. Google may work from a limited narrow perspective, but the needs of the organisation are what typically push it to 365 as it has Teams, Stream, Forms, PowerApps, Power BI, and much more: all of this can be controlled from an enterprise perspective with Intune or SCCM. If your users are using Windows for the main, obviously 365 is designed to work natively with the OS.
I could evangelise all day - however, I think you already know hence reaching out here. The community can and will support you on this so keep in touch and I hope it goes well.
Best, Chris