Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Businesses Microsoft

Microsoft Is Killing Yammer Enterprise in January 2017, Will Start Integrating Office 365 Groups First (venturebeat.com) 44

Microsoft today provided new information about how it will be integrating Office 365 Groups into its Yammer enterprise-focused social network. The Yammer Enterprise service tier will be going away on January 1, 2017. But Yammer itself will remain available, and there are many levels of integration with the Office 365 services, reports VentureBeat. From the report: It will be possible for people to make Word, Excel, and PowerPoint documents using Office Online within Yammer, and it will be easy to go from Yammer to a shared OneNote notebook or the Microsoft Planner project management tool. Team members will be able to select existing files from OneDrive and SharePoint and share them with colleagues in Yammer, too. And Yammer teams will get their own SharePoint sites, enabling them to build wikis and blogs. Microsoft will be rolling out the integration in phases, with the first phase beginning later this year, the Yammer team said in a blog post. The first Yammer customers to get it are those whose users log in with their Office 365 identity. And Microsoft will initially be targeting organizations with a single Yammer network connected to one Office 365 tenant.
This discussion has been archived. No new comments can be posted.

Microsoft Is Killing Yammer Enterprise in January 2017, Will Start Integrating Office 365 Groups First

Comments Filter:
  • by Anonymous Coward

    First time I hear about this product.

    • by The-Ixian ( 168184 ) on Tuesday September 27, 2016 @01:07PM (#52970417)

      It is a good solution for companies who don't want to rely on a public social networking site.

      I have worked for a few large companies who have run a Yammer site. It is basically just an internal company Facebook.

      It can be used for good purposes. Stuff that doesn't necessarily fall into "official" company communiques or which might fall outside company org structure.

      For example, charitable events that company employees participate in might have a Yammer group... stuff like that.

      The fact that it incorporates into AD and as well as other MS Office tools and products makes it attractive for organizations already in the MS ecosystem.

      • It's very well suited for certain work-related stuff as well. Virtual town hall sessions. Community-based support, especially for services where a lot of new things are happening (so users will want to subscribe to the group and remain informed). Virtual, cross-departmental team spaces. Communities of Practice. I've been involved in setting up Yammer and coaching community managers at my last client, and we've experimented with a great many use cases. Most successful cases were in the category of fast
    • And last thing I want to hear about: "enterprise-focused social network"

  • by Pascoea ( 968200 ) on Tuesday September 27, 2016 @12:33PM (#52970171)

    And Yammer teams will get their own SharePoint sites

    "I can't wait to use Sharepoint more" -No one, ever.

    • Re:Yay! Sharepoint! (Score:5, Interesting)

      by bigman2003 ( 671309 ) on Tuesday September 27, 2016 @01:33PM (#52970571) Homepage

      I'm a Microsoft flag waver- for the last 20 years. It's been core to my career.

      I absolutely hate Sharepoint, and I hate the way they are integrating it into everything.

      Recently I had someone come to me saying that they kept sending out files, and nobody outside of our organization could access them.

      Their files were saved to Sharepoint (the default, not their intention) and when they 'attached' the file to an email, Outlook went ahead and sent a link, rather than attaching the file. The link went to our internal Sharepoint, which people on the outside could not access.

      I understand all the reasoning for this to happen. But the problem was that this was just a naive user clicking 'Sure, save it there, that is cool' then being stuck in this problem. I told them to save the file elsewhere...but now they had two versions of the file and confusion ensued.

      Please, please, please don't make 'further integration with Microsoft products' the default!

      And no...nobody has ever wanted to use Sharepoint more. I've been around it for a long time, and I don't understand what the heck it is supposed to be. Ignoring all Sharepoint is a valuable skill.

      • The integration is the selling point (for the decision makers, anyway). It's what differentiates it from other standalone solutions for what SP is trying to be. And that's the funny thing: SP is trying to be a lot of things. Document management: does a sucky job and misses basic features that our 15 year old software did have. Wikis: dear god, you're better off with MediaWiki and a couple of good plugins. Message boards: sort of work, but again misses a lot of basic stuff (such as rules-based community
        • by PCM2 ( 4486 )

          From what I can tell (haven't actually tried it), it looks like it would take months to get a stock SharePoint install hammered into some form that would actually be useful for your organization. Out of the box it's practically useless. You'll be paying those couple of consultants whether you go with Microsoft or not.

      • by swb ( 14022 )

        My guess is that MS really wants to kill of basic (SMB) file sharing. The protocol is open enough that world+dog has already implemented in everything, so every file server upgrade faces the prospect of losing out to something else -- shit appliances all the way up to big ticket EMC devices.

        Trying to move everyone to Sharepoint has so many layers of lock in I get dizzy just thinking about them. The endless licensing sales for server, SQL and 3 different kinds of CALs. Relentless sunk costs of developer t

      • by PCM2 ( 4486 )

        Their files were saved to Sharepoint (the default, not their intention) and when they 'attached' the file to an email, Outlook went ahead and sent a link, rather than attaching the file. The link went to our internal Sharepoint, which people on the outside could not access.

        The default in Outlook 2016 is to also send links when you attach files that are in your OneDrive folders. That is, to you it seems like you're navigating through the filesystem and attaching a file, but Outlook "helpfully" sees that it's synced to OneDrive and sends a link to the website instead. There's a little box or something you have to check if you want the classic behavior, but you have to set it every time you send an email. I couldn't find any global setting to disable the linking.

      • and I don't understand what the heck it is supposed to be

        Sharepoint is supposed to be everything based on the marketing and the typical way it's setup in most companies.

        That's also why it's so popular. Jack of all trades and master of none, actually not even novice at most really all things considered. But if you wanted 1 vendor and 1 platform to try and do bloody everything then Sharepoint is a skill that will put bread on the table.

      • I'm a Microsoft flag waver- for the last 20 years. It's been core to my career.

        20 years is really a long time in antivirus development and security consulting...

  • That's what Microsoft always does: buy a company, and destroy it.
  • This is the main reason why I hate cloud products, Simon says, and we are all fucked up, can't count the number of times I have had to relearn Office 365 crap , for something as simple as get a fucking invoice. Google is even worse, they are like, tomorrow, no more feature for you, need support? Ask the community, good luck!

  • Microsoft Haiku (ish):
    No vacation
    Work every weekend
    Office 365

    And I understand that they're ripping off "Whole Foods 365" brand, but I like drinking orange juice every day. Office work 365 days a year? No thanks -- but it is the society we are becoming.

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...