Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Leveraging Microsoft Teams for a SharePoint-Centric Organization

515 views

Published on

From Oct 26, 2017 webinar with Microsoft MVP Christian Buckley (@buckleyplanet) hosted by PixelMill (@pixelmillteam) on how to make Microsoft Teams your secret weapon to becoming a stronger organization. The session gives an overview of Office 365 Groups, as well as Microsoft Teams, including provisioning, what happens behind the scenes as multiple workloads are established, and productivity and extensibility features of Microsoft Teams that will undoubtedly have an immediate effect on employee adoption and engagement.

Published in: Technology
  • Be the first to comment

Leveraging Microsoft Teams for a SharePoint-Centric Organization

  1. 1. CHRISTIAN BUCKLEY | Founder/CEO of CollabTalk LLC Microsoft MVP LEVERAGING MICROSOFT TEAMS FOR A SHAREPOINT-CENTRIC ORGANIZATION www.pixelmill.com @pixelmillteam #PixelMillWebinars
  2. 2. Christian Buckley Founder & CEO of CollabTalk LLC Office Servers & Services MVP cbuck@collabtalk.com www.buckleyplanet.com @buckleyplanet
  3. 3. About CollabTalk CollabTalk is an independent research and technical marketing services company. We take a collaborative approach to everything we do, augmenting our capabilities with a deep network of partners and community influencers. Customers include many well-known brands within the Microsoft ecosystem:
  4. 4. The successful adoption of Microsoft Teams requires a change in behavior for most organizations. Teams is more than a product – it represents a different way of working. Change is about people – and re-wiring corporate culture.
  5. 5. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  6. 6. What is your collaboration culture?
  7. 7. Scenario 1  Meet Stephanie  Web developer, millennial  Personalization is important  Lives on her mobile device  Very collaborative, in constant contact with her team, sharing ideas and discussing the state of customer projects  Values real-time interactions, having fun while working, and is very passionate about her work
  8. 8. Scenario 2  Meet Tasha  Program Manager  Responsible for several key business processes  Has worked to develop several form and workflow-based sites to help automate and ensure that her team is compliant  Her team includes a number of attorneys and financial analysts, who prefer in-person meetings  She spends a lot of time working in email, and manages a number of vendors and parallel projects
  9. 9. Scenario 3  Meet Hugo  Customer Success Manager, business development  Manages a number of projects and events with large teams of external vendors and partners  Very involved in the customer community  Helps drive their partner and customer portals, provides online and in-person product training  Also manages his company’s social profiles, interacts with customers and partners wherever they congregate
  10. 10.  Real-time  Team-based  Persistent chat  In-person  Process-based  Email  Mix  Community-based  Social
  11. 11. The reality is that most organizations have all three With differences across your business – or even within a single team or business unit
  12. 12. Which tool to use when?
  13. 13. WHAT IS THE RIGHT USER EXPERIENCE? Wants real-time communication Wants process and structure Wants community and transparency
  14. 14. It Depends. What is the right solution for your org?
  15. 15. Office 365 Groups ↓ Microsoft Teams ↓ Bots, Connectors, and Tabs
  16. 16. Where Does SharePoint Fit?
  17. 17. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  18. 18. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  19. 19. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  20. 20. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  21. 21. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  22. 22. https://www.slideshare.net/SPSParis2017/keynote-mark-kashmann-sps-paris-20171014
  23. 23. Microsoft Teams 101
  24. 24. Creating the Intelligent Enterprise  Tabs  Connectors  Bots
  25. 25. Adding Tabs
  26. 26. What Tabs Can Do  Provide an interface into relevant content  Surface sites and tools in context to conversations  Remove the “which tool do you use when?” argument
  27. 27. Adding Connectors
  28. 28. Adding Connectors https://msdn.microsoft.com/en-us/microsoft-teams/connectors
  29. 29. What Connectors Can Do  Push rich content to Microsoft Teams  Connect to services like Trello, GitHub, Bing News, Twitter, etc.  Receive notifications of team activities for each service / stay in sync  Complete tasks within a channel
  30. 30. Leveraging Bots
  31. 31. What Bots Can Do  Automate manual tasks  Enhance a conversation thread  Act as a personal assistant to find information and content  Ability to answer natural language questions  Run surveys  Provide quick status updates on open projects and tasks, kick off workflows, etc  Improve the user experience
  32. 32. Microsoft Teams includes two primary bots:  Who-Bot is a quick reference tool for engaging with your team members.  Users can enter real-language requests, such as “Who on my team has experience with manufacturing technology” and the Who-Bot will reply with team member names and contact details, based on profile data, content ownership, and use of keywords within conversations.  Leverages the Microsoft Graph to learn from your collaboration and communication patterns, acting as the ultimate personal networker for your company.  T-Bot is an assistant to help you get the most out of Microsoft Teams.  Provides guidance on the growing set of features in Teams.  Ask the T-Bot “How do I add a connector?” and it will provide the answer through the relevant Help topic.
  33. 33. Let’s see a demo…
  34. 34. Governance and Administration
  35. 35. Office 365 Security and Compliance Portal  Auditing and Reporting  Audit log search plugs right into the Office 365 Security and Compliance Center and exposes abilities to set alerts and/or report on Audit event by making available, export of workload specific or generic event sets for admin use and investigation, across an unlimited auditing timeline. All Audit Log data is available for setting up of alerts within the Office 365 Security and Compliance Center, as well as for filtering and export for further analysis.  Compliance Content Search  Content Search can be used to search Microsoft Teams through rich filtering capabilities and exported to a specific container for compliance and litigation support. This can be done with or without an eDiscovery case.
  36. 36. Office 365 Security and Compliance Portal  eDiscovery  Electronic discovery is the electronic aspect of identifying, collecting and producing electronically stored information (ESI) in response to a request for production in a law suit or investigation.  Capabilities include case management, preservation, search, analysis and export of Teams data. This includes chat, messaging and file data.  Customers can leverage in-place eDiscovery or Advanced eDiscovery  Legal Hold  When any Team within Microsoft Teams is put on In-Place Hold or Litigation Hold, the hold is placed on the groups mailbox.  Legal Holds are generally applied within the context of an eDiscovery case.
  37. 37. Office 365 Security and Compliance Portal
  38. 38. Security Concerns with Bots  The current slate of bots act as “passive” controls within the system, which means they are not actively “listening” to your content and conversations, and must be activated or “invoked” to take action.  Most users will not take the time to understand the security impacts of using a selected bot. If a bot *can* be added, most corporate employees assume it has been “vetted” by IT, and is safe for use.  Security for bots is at the end user-level.  Understanding what each bot does, and whether or not they send data outside of the organization, should be part of your security planning.  Enabling bots is currently an all-or-nothing decision – you can either allow users to add bots, or turn off access to all bots for your organization.
  39. 39. Bot Discovery
  40. 40. Future Features  Microsoft is considering providing the following security features for Teams. Once available, guidance will be provided on how customers can leverage the features: • Tenant-specific retention Policy • Data loss prevention (DLP) • Customer Lockbox • Right Management
  41. 41. Auditing Microsoft Teams  The Audit Log provides ad- hoc search capabilities for Microsoft Teams through the Security & Compliance Admin Center, including: • Team Creation • Team Deletion • Added Channel • Changed Setting
  42. 42. Conversation eDiscovery  All Teams 1:1 or group chats are journaled through to the respective users’ mailboxes and all channel messages are journaled through to the group mailbox representing the Team.  Files uploaded are covered under the eDiscovery functionality for SharePoint Online and OneDrive for Business.
  43. 43. Groups Best Practices  Control their rollout  Clearly define and enforce a naming convention  Be careful about Groups creating from other workloads – be aware of what is being provisioned, and ensure that company-wide policies are being met
  44. 44. Microsoft Teams Best Practices  Control provisioning through IT  Enforce your naming conventions (SharePoint Online Managed Path)  Schedule regular, recurring training for employees  Backups through SharePoint and Exchange workloads  Manage navigation sprawl through ‘Favorites’  Be aware of available Connectors and Bots and what they do  Drive people toward following + sharing through Channels
  45. 45. Office 365 Usage Analytics
  46. 46. www.SuccessWithTeams.com
  47. 47. Christian Buckley cbuck@collabtalk.com @buckleyplanet Thank you very much!

×