08-09-2018 09:21 AM
08-09-2018 09:21 AM
You guys seem to have a bit of ADD when it comes to collaboration applications these days. I kind of thought everything was starting to come together with Teams being new flagship product, but then I see you release Kaizala to Office 365 users. What exactly is the strategy here?
04-04-2019 12:01 PM
@Karuana Gatimu Thanks for the clarification - Just saw the message on Kaizala rolling out globally, and was wondering "why another chat". The clarification below "If your organization is committed to Office 365 and Teams there's no need to deviate from that" helps.
It would be helpful if there was more clarity about the use case for these apps when a communication like this comes out. It would also probably save you a lot of grief from people like me as well.
04-05-2019 07:32 AM
Hi there - I'd be interested in your comparison of Slack vs Teams and where you thought Slack didn't work for you.
04-05-2019 09:15 AM
Sorry - I wasn't clear. I've not used Slack before, at least not in any serious way.
04-06-2019 05:26 AM
04-12-2019 02:17 PM
Funny you state "If your organization is committed to Office 365 and Teams there's no need to deviate from that." because that's what MS has been 'advising' us from day one. We have been told, "Teams will be the hub for EVERYTHING Microsoft". We were event told that eventually, we wont even need Outlook anymore' it will all be done from within Teams.
Yet here is another product/service that offers some value, overlaps with value already in other services/products and I still don't get it. I understand your examples and I get that however, it seems there is no thought given to the existing MS customers how have already invested in existing services/products.
This just adds one more and to a lot of customers, our users are constantly coming to us with "now what's this new app, are we supposed to be using it, I thought XYZ already did that we were instructed to use that"?!
To make it worse, like always, the new service is on by default and we have to actively go in and prevent the new service from appearing. It's a constant battle and I agree with others that you are shooting yourselves in the foot.
When the circle becomes to large to manage, we will start to look for more streamlined, manageable solutions.
Take all these one-off services and products and integrate them into the core services already being consumed.
My full time job is not staying on top of "What's MS doing this month". We have asked repeatedly for a M365 Road Map and its gotten too big for even MS to present. We were told, there are too many services to present a Road Map. Even with Ignite, who can keep up anymore.
04-12-2019 02:28 PM
@KeithT I definitely agree with your concern when it comes to these communication tools that do the same thing and the humor is not lost on me that this blog posting messaging thing we are using on this website is yet another variation of a similar thing (as is VSTS).
When it comes to the roadmap though...I think they do a great job on this site...
I give them an A+ for having that site.
04-22-2019 09:12 AM - edited 04-22-2019 09:29 AM
Here is my take on things:
What if we have different "Channel Types" in a single Solution.
If you cancel out the overlaps of each solution, what are you left with ? The scenarios itself.
Solution = Teams
Channel Scenario = Choose a scenario type for this channel that suite your needs.
Each Channel Type can be configured to allow for the different scenarios.
Private, Open, Closed, Non-AAD, Public Directory Listing, Low-Bandwidth, Telephone Number method, Outer Loop, Inner Loop, IM Chat, Dial-In. etc. etc. etc.
Teams is about unification of islands yes, love it but is now being muted out by introducing overlaps of other solutions instead of having the ability to define scenarios per channel.
05-06-2019 04:49 PM
Honestly, this just seems like a Microsoft version of What's App. If that is the vertical, it makes sense and I can see it being a good competitor. Integrating this into Teams is confusing users, though. I would agree that is it gumming up the communications strategy. Having used Kaizala (mind you, the name is not good), I can see a use. Again, this is a What's App look-a-like.@Karuana Gatimu
05-06-2019 04:57 PM
You can give access to outsiders in Teams, but it is a royal pain. Yammer can do this with external people quite easily and works good. Kaizala in my opinion is easier than teams to collaborate in that I do not have to log out of my tenant.@Michael Fulton
05-06-2019 04:59 PM
OK...so maybe its a dummied down GUI for a subsetted use case...fair enough, but the problem is integration. A Kaizala user can't message a Teams user or Skype For Business user or a Yammer user. At the very least these GUIs should be able to interoperate. I'd personally prefer one platform though. You could have a Teams Communicator Mobile client...only does messages. A Teams Files Mobile client...only manages files. A Teams Full GUI mobile client that has everything. You can always dummy down a smart app with out splitting the platform and creating a new isolated island of users.
05-06-2019 05:05 PM
Sorry, but I have to agree with everyone else...Kaizala is confusing the Microsoft communications ecosystem. First of all, Groups needs to die out quickly. It is really old, clunky and is overall a bad technology. Along with Groups, Sharepoint needs to die a hard death. Not only is it only an clunky, but it is holding Microsoft's best technology back from being great. OneDrive is slow and clunky because of its Sharepoint underlining. I will say this, Kaizala and Yammer are super fast and fluid. I would attribute Yammer's speed to it not being build on the Sharepoint foundation. Planner is a great idea, but royally stinks because of Sharepoint. Honestly, I would love the opportunity to help Microsoft fix these issues. Unfortunately, this rising generation of users is all about Gmail, Trello and Dropbox because they work fast and fluidly.@Karuana Gatimu
05-07-2019 04:57 AM
05-07-2019 06:03 AM
While I do appreciate what you are saying, I do not find SharePoint as clunky, at this point in our deployment.
With Teams, I have an integration point for almost everything within our environment. Being able to attach team sites to a Hub site has helped the integration into our SharePoint environment. Office 365 Groups is that attaching point that we are utilizing. Even Yammer allows integration into SharePoint and Teams.
I do agree that Kaizala is confusing the communications ecosystem, but we do not know whom Microsoft is targeting with this offering. From everything I have seen in Office 365, there is a method to their madness. We just do not know what it is at this point in time.
06-18-2019 10:25 AM
@Karuana Gatimu I understand the use case for Kaizala in emerging markets and easy on-boarding of users. Thank you for the clarification of where it fits in.
Here is what I don't understand, as an Office 365 Admin who is trying to increase adoption of Teams and migrate from Skype for Business. Why is Kaizala forced on us by default and why are the user controls so limited for an Admin? This morning we came in to find that Kaizala licenses had been enabled for all of our 100,000 + users in our tenant. So, that means the Kaizala app will now appear in the app launcher. This is not an unusual scenario for us, so we read up on how to disable Kaizala for our tenant in O365 Admin Center. Short answer, we cannot.
So, we have to dig in and find the Kaizala Management portal. We can disable Kaizala for our organization from that portal. However, that does not remove the app from the O365 app launcher, it just prevents our users from logging onto Kaizala with their O365 organization credentials. So now we have to sweep thru all users and disable Kaizala license until we have the opportunity to understand the app and figure out if we can support it. Then we need to figure out how to communicate where it fits in with all the other messaging and collaboration tools we support.
Our main feedback here is:
Don't enable new app licenses by default and if you do, please provide consistent methods of disabling the app for larger organizations.
06-18-2019 12:04 PM
Egad @Tim Crean...us to...just like that new app roles to thousands of users with zero change management. Really Microsoft? Just really?
06-19-2019 05:02 AM
06-19-2019 05:41 AM
There is good and bad in opening the gates. Most people do not know more than just the Office suite. I am finding it difficult to get people to look at the portal, even my IT department. People are so set in their ways that, majority of the time, people will never find out.
We have everything opened and available for people to use. I am doing this so that I can get some grass roots support for many of the M365 applications. But, it is going no where fast. If I do not tell people about a capability, it will go unnoticed.
Adoption is the key to all of M365. Just need to find that business case and go with it.
06-19-2019 06:02 AM
06-19-2019 08:38 AM - edited 06-19-2019 08:41 AM
06-19-2019 08:44 AM
On my side, people were CONVINCED that competing Apps, without mentioning, were the best but since I introduced Teams AND explained on a whiteboard how each O365 App looks and represents the SAME data from each perspective and why, they immediately understood the eco-system drive that MS is pushing for. I was able to convey WHY each app is there: Delve, Planner, Stream, etc.
I'm hoping to get to this part...