{"id":10906,"date":"2019-11-29T12:17:06","date_gmt":"2019-11-29T20:17:06","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=10906"},"modified":"2023-06-16T13:39:57","modified_gmt":"2023-06-16T20:39:57","slug":"redefining-the-intranet-site-experience-with-sharepoint-in-office-365","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/redefining-the-intranet-site-experience-with-sharepoint-in-office-365\/","title":{"rendered":"Redefining the intranet site experience with SharePoint in Office 365"},"content":{"rendered":"
\n
\n
<\/div>\n
This content has been archived, and while it was correct at time of publication, it may no longer be accurate or reflect the current situation at Microsoft.<\/p>\n<\/div>\n<\/div>\n
SharePoint Online is continuously updated to provide a flexible collaboration framework. Recent enhancements to communication sites and hub sites improve collaboration and drive engagement. SharePoint sites deliver attractive, personalized experiences, integrate seamlessly with Office 365, and carry reduced development and design costs.<\/p>\n
Microsoft Digital provides and maintains the infrastructure and technology to enable effective collaboration for more than 220,000 Microsoft users. Content-driven collaboration at Microsoft is powered by Microsoft SharePoint for Office 365 and its integration with the rest of the Microsoft Office 365 suite and our broader cloud environment.<\/p>\n
Over the years, SharePoint has dramatically improved the quality, accessibility, performance, and usability of the base platform for users as well as publishers. Contemporary SharePoint features like communication sites, hubs, and modern groups have been fused with foundational elements like search, taxonomy, and the user profile service to form the backbone of the Microsoft intranet.<\/p>\n
The new, modern platform reduces the need for custom development, saving Microsoft Digital time and money. Where development is needed, we can now take advantage of robust new development capabilities in the SharePoint Framework (SPFx) and the client-side web parts they enable to develop and publish attractive, highly functional intranet sites.<\/p>\n
Thanks to SharePoint\u2019s new flexible, modern architecture, we\u2019ve successfully transitioned more than 75 percent of our internal publishing sites to the modern communication site.<\/p>\n
The SharePoint landscape at Microsoft<\/h2>\n
SharePoint has a long history of being the primary collaboration platform for our intranet and extranet solutions at Microsoft. Our first corporate communications portal built on top of SharePoint debuted in 2002 and has been updated to work on every version since.<\/p>\n
Historically, we hosted on-premises SharePoint Server infrastructure in our on-premises datacenters within our perimeter network. After the internal rollout of SharePoint Online in 2011, we worked with our internal business to convert all of our major sites for internal functions\u2014HR, legal, finance, communications, sales, and learning\u2014to SharePoint Online.<\/p>\n
Traditional design and deployment<\/h3>\n
For years, SharePoint was designed to provide a starter platform on which interesting sites could be built. Although powerful, the default, out-of-box sites had some shortcomings:<\/p>\n
\n
The default site template was nondescript and basic.<\/strong>\u2002If site owners wanted to build an attractive site, they had to go above and beyond the default template. This meant extra work for developers and extra steps in the publishing process.<\/li>\n
Customization was developer intensive.<\/strong>\u2002Customization of site functionality, navigation elements, and design required developer involvement. Achieving a user experience that the business would be happy with required a heavy investment in the configuration and customization of master pages, CSS, JavaScript, and web parts.<\/li>\n
Sites were not responsive by default.<\/strong>\u2002The traditional site types were designed for a PC browser, and the mobile rendering of traditional sites often produced unattractive or partially nonfunctional results on mobile devices.<\/li>\n
Sites were not accessible by default.<\/strong>\u2002Accessibility in the classic SharePoint templates wasn\u2019t up to our current standards. As a result, our intranet sites didn\u2019t provide proper interaction with tools like screen readers or high-contrast color schemes by default. Meeting accessibility standards required design and developer effort.<\/li>\n<\/ul>\n
To mitigate some of these challenges, Microsoft Digital engineering teams developed custom SharePoint design templates that gave site owners a head start on building an attractive, useful, accessible, and responsive site experience. By applying these custom design templates, we could jump start the build process while saving businesses time and development budget. The templates were effective, but they required ongoing development and maintenance.<\/p>\n
Our move to the cloud<\/h3>\n
Microsoft has been a cloud-first organization since 2012. Our organization runs on cloud computing, and that cloud-first ethos is reflected in how we\u2019ve treated our SharePoint infrastructure. We\u2019ve moved our SharePoint infrastructure out of our on-premises datacenters and into Microsoft Azure and Office 365 to take advantage of cloud agility, scalability, and reliability across our IT infrastructure.<\/p>\n
Cloud-based collaboration provides several essential advantages:<\/p>\n
\n
All sites and tools are in one service, from one vendor.<\/li>\n
Personal and business sites are all within the same administrative and functional scope.<\/li>\n
All sites are designed, developed, and managed with the same toolset and in the same environment.<\/li>\n<\/ul>\n
Hybrid cloud content management<\/h4>\n
Our current environment is hybrid by design, but the vast majority of our SharePoint sites are now hosted in SharePoint Online. Although we still retain some data and apps in the on-premises environment, the reasons for doing so are mostly limited to maintaining functionality with older business information systems and apps and uncommonly large org-to-org extranet scenarios.<\/p>\n
Thanks to advances in SharePoint Online, these exceptions are now rare enough that we\u2019ve successfully moved more than 99 percent of our SharePoint site collections to the cloud.<\/p>\n
Enabling self-service and creative collaboration<\/h3>\n
Self-service site creation lowers barriers to effective collaboration, so we make it possible for all of our users to provision sites to meet their business needs. In doing so, we create an environment in which our users can collaborate in a way that best suits their particular needs. With SharePoint Online, our users determine what kind of sites they can create, execute on that creation, and administer their own sites.<\/p>\n