Sharepoint   25573

« earlier    

Twitter
Thoughts on learning, passion and public speaking by , Microsoft MVP
SharePoint  from twitter_favs
9 days ago by geertbaeke.info
How to sort through redundancies between SharePoint and Office 365
Sharepoint
The standard team site has surely been one of the platform's most popular templates, enabling document sharing, team tasking, communication, scheduling, project tracking and notification functionality in a single location

Microsoft Teams
Microsoft's Teams application, upon which it has placed high hopes, is being leveraged to compete with Slack. Teams facilitates the creation of ad hoc workgroups in the enterprise, cloud-based communications for project or task discussion, planning, and record keeping. Documents, links and other useful artifacts can be appended to chats and tagged, as well. And everything can be saved for later reference

Office 365 Groups
by default, provisions a new group with a Team, Yammer and a SharePoint team site.

First Cut
If your collaboration is lean and mean, spontaneous, and simple, go with Teams; if it's complex and in need of careful tending and tight security, go with SharePoint

Other Use Cases
- Is the project gathering together a significant amount of content that will later be needed elsewhere? Go with SharePoint (the creation of a new Team passively provisions a team site for document storage anyway, so Microsoft is leveraging its tried-and-true SharePoint document libraries in any case).
- Are multiple user platforms required? Go with Teams; it works well on Windows, Mac OS X, iOS and Android.
Will APIs be required to tie project activity to external apps? Teams can't do that; go with SharePoint.
- Need real-time chat? Choose Teams; SharePoint Newsfeed has been deprecated (though Yammer can be embedded in SharePoint).

CONTENT MANAGEMENT
The simple rule of thumb: For structured or custom content, go with SharePoint; for simple, Office-compatible content, go with OneDrive.

Other use cases
- Does the content need to be customized? For custom views, metadata and configurable data types, go with SharePoint.
- Is there a need for personal file management across devices? OneDrive is built for that.
- Does management of the content require a custom workflow? Go with SharePoint.
- Will larger files need to be readily emailed? Go with OneDrive.
- Does the content have complex security requirements? Go with SharePoint.
microsoft  sharepoint  office365 
10 days ago by tom.reeder

« earlier    

related tags

2013  accdb  access  app  application  applications  approval  apps  aspect  azure  blog  bookmarks  bugs  catalog  claims  cloud  columns  command  community  connect  content  cookies  corrupt  corruption  crm  csom  cswp  custom  customization  damage  database  default  deploying  designer  developer  development  disasterrecovery  discussionboard  email  epiuse  excel  external  externalsharing  extranet  form  formulas  forum  framework  hash  iis  inheritance  intranet  javascript  list  lists  microsoft  migration  modern  modern_sites  ms  msdn  noscript  o365  office365  office365groups  onedrive  online  pdf  permissions  powershell  profile  report  reporting  rest  salient  sdk  search  security  server  servergraph  services  sharegate  sharepoint  sharepointonline  site  sizing  skype  slider  slideshow  solution  spfx  sql  sql2017  sqltact  ssis  ssl  ssrs  survey  team  teams  threshold  update  user  view  web  webhooks  workflow  yammer 

Copy this bookmark:



description:


tags: