Forum Widgets
Latest Discussions
Manage Yammer users across their life cycle from Office 365
After Yammer is activated on your Office 365 tenant, you, as the Office 365 administrator, can control the life cycle for Yammer users from Office 365. When you create users in Office 365, they can log on to Yammer with their Office 365 credentials. When a user is deleted from Office 365, they are automatically deactivated or suspended in Yammer. When a user is restored in Office 365, they are reactivated in Yammer. Also, the user's profile properties (such as name and department) from Azure Active Directory will be automatically populated in the user's Yammer profile, and any changes to the profile properties in Azure Active Directory will be reflected in Yammer as well. Learn more on how to manage, add, block, and delete users here.What's new in the Viva Engage Admin Center - now on the web!
Check out What’s new in Viva Engage Admin Center - Microsoft Community Hub Updates include... Viva Engage Admin Center on the web Redesigned Data Export now available on the web Manage owners and members for communities in Viva Engage that don't have an admin as the owner Viva Engage Admin Center updates coming soon... Provide tenant configuration capabilities like setting usage policy and uploading organization logo in the new experience Provide file and rich media permission capabilities like enabling GIFs in the new experience Stay tuned with what's coming next by following the Microsoft 365 Roadmap.
How does Sanofi Pasteur use Yammer to transform corporate culture and prevent disease?
We are very excited for the world to hear about the Sanofi Pasteur story! Sanofi Pasteur is responsible for making some of the world’s most complicated and vital products. Read how the company uses Yammer to further its mission of protecting lives with vaccines. https://o365.com/sanofipasteurHappy M365 Conference Week!
We are so excited to have MichaelHolste espnguyen and danholme in Las Vegas with some of our customers and partners at M365 Conference! We have a great line up of Viva Engage sessions and can't wait to see many of you in person. Join us at the booths to catch up and ask questions. “Viva Engage - What's New and Next” with Steve Nguyen and Dan Holme “Viva Engage for leadership and communications” with Dan Holme “Answers in Microsoft Viva” with Michael Holste More details can be found here: Microsoft 365 Conference event guide to keynotes, AMA, sessions, and more Stay tuned and learn more by checking out M365Conf.com and follow the action on Twitter: @M365CONF!Generating an Administrator Token
The administrator functions built into Yammer work well, but what if you want to perform an administrator function outside of what's built for you? If you ask around, you may find someone advising you to take advantage of the REST API, but if you don't know where to start, then you've come to the right place. Because you can't fully use the REST API and you can't run any of the scripts posted in this community if you don't have a token. This token is like your username and password, and is what allows you to tell Yammer that the script you're running is you. Getting one of these things used to be relatively complicated, but is much simpler now. Step 1: Log into Yammer normally, then click this - https://www.yammer.com/client_applications Step 2: Click the big green box, Register a New App Step 3: Fill in the form. The name can be whatever you want, and the organization and email should match what is approprate for your organization. I always use Yammer as the redirect URI. Step 4: Now you're on the information screen and can go get your token. On the bottom of the screen is a link called "Generate a developer token for this application". Click that. Like magic, your very own scripting token will now appear. Copy and paste that into something safe and secure. Remember, this is your username and password all rolled up into one, and if someone gets that, they can perform the same functions on your network as you can. Guard it carefully. And then use it for the scripts you'll find elsewhere in this community. Enjoy!
Default Sharepoint Permissions Set to Everyone for Public Communities
In native mode, it appears that when a new community is created as public, the corresponding sharepoint site that is created gives "Everyone except external users" site member access. This means that even users who are restricted from using Viva Engage via the option to block unlicensed users are able to see files and resources that have been uploaded to that community. This is a particular problem in environments where some users need restricted access, such as Students in an education environment. Is there a way to change this behaviour, or set a default public group? The only solution we can think of is to either set all communities to private (which diminishes the user experience of Viva Engage), or to ensure that Sharepoint permissions are updated manually whenever a new community is created. Any help greatly appreciated.Is there any kind of email or notification that is pushed when someone uses Storyline?
As per the title, I'm wondering if M365 will push out an email or any kind of notification is someone uses Storyline - assuming: no topics were used no one is FOLLOWING the individual no one is mentioned Would the 'Discover what's happening across your organization' auto-digest include storyline posts that no one has seen or engaged with?
