04-17-2018 04:18 AM
04-17-2018 04:18 AM
Microsoft Teams can be used for a variety of purposes. The user cases are many and, as usual, it's usually just the imagination that sets the limits of creativity.
Today's new technology has a high degree of self-service and when new functionality is rolling out at an ever increasing rate, it is often easy to forget how to enable end-users to take advantage of the new functionality.
Having good documentation about managing personal data is becoming increasingly important, not least in terms of GDPR. You also need to plan how to inform the end users in the most efficient and educational ways about news and changes in order to succeed with user adoption. Not least, it is important, as a "service responsible", to keep up to date with new functionality to take advantage of the services that make the most of the organization's needs, requirements and goals. These points, in my opinion, are advantageously mentioned in context of Office 365 Governance.
In this post, I will show how to set up a Team to get started with Office 365 Governance in the easiest way possible.
I start by setting up a Team and configure the Channels and their tabs.
Under the General channel (which, by definition, should contain general information) I do the following:
I create a Channel and call it Activity alerts. This channel I use to capture "general" (not related to a specific service) alerts from the Security and Compliance center. This may, for example, be if someone has deleted a user or if any administrator has been granted extended privileges. I copy the channel's email address and enter it on the alert I set up in the Security and Compliance Center under Activity Alerts. In this way, I do not have to log in as Global Administrator to get an overview of the general alerts I set up. However, to see details, I have to log in.
If I do not exercise Change Management "by the book" I should at least have a simple process to keep track of changes and news so that I have the ability to plan for the introduction of them.
I create the channel "Change". Under the channel I do the following:
For each channel that belongs to a service I capture service-related alerts from the Security and Compliance center. This may, for example in the Channel for Microsoft Teams, be if someone has deleted a Team. I copy the channel's email address and enter it on the alert I set up in the Security and Compliance Center under Activity Alerts. In this way, I do not have to log in as Global Administrator to get an overview of the Service-related alerts I set up. However, to see details, I have to log in
Under the channel for Microsoft Teams I do the following:
Each service (Teams, SharePoint, Yammer etc.) should have its own channel that contains tabs for Roadmap filtered on the service, Governance Plan for the Service and the service-related activity alerts should be set up for each service.
The governance plans, of the various services, and their content and disposition are something that you can and should establish based on the parameters that are important for your company to control.
This post is not the answer to how everyone should manage Office 365 Governance but I hope it gave you something useful that you can take advantage of if you wish to get started with basic governance for Office 365.
If you have any questions or suggestions, please comment on the post or send me a message.
09-12-2018 05:48 AM
Hello Dean, I am internal to Microsoft, specifically in the Education space. I am evangelizing this particular use case internally. It's a strong example of how Teams can be used with a lot of benefit to O365 admins. Nice work @Magnus Goksøyr
09-12-2018 03:17 PM
09-12-2018 03:17 PM
Thank you very much for your reply Magnus! It's a very good idea to have an owner per service, so at least one person has deep insight into how the service has been used. I also like the idea to seperate each individual service out of the overall O365 governance.
Again, thank you for sharing your ideas! They are very helpful!
by Magnus Goksøyr on June 25, 2018
by Magnus Goksøyr on April 17, 2018
by MicrosoftTeamsTeam on July 21, 2020
by Robert Schouten on November 19, 2019
by Aya Tange on March 20, 2019