Hybrid

Hybrid Self-Service Site Creation now available for SharePoint Server 2013

@williambaer

At the center of collaboration is the site and modern Team Site in Office 365 are core to discovering and showcasing the most relevant and important information to you and your business. While SharePoint Online in Office 365 is an attractive alternative to on-premises business solutions with SharePoint. You might want to or need to deploy specific solutions in the cloud while still maintaining your on-premises investments or gradually move to cloud using a staged, workload-driven approach.

Hybrid scenarios with Office 365 and SharePoint on-premises allow you to bring the cloud to your business while bringing the business to the cloud. Today we’re pleased to announce the availability of hybrid self-service site creation for customers of SharePoint Server 2013.

New hybrid self-service site creation allows SharePoint administrators to direct users site creations requests to Office 365. This new hybrid capability allows administrators of SharePoint Server 2013 to have the option to enable their existing or new Self-Service Site Creation flow redirect users to SharePoint Online to create a Group (with an associated Team Site). SharePoint administrators can turn this feature on or off on the Self-service Site Collection Management page, accessible from SharePoint 2013 Central Administration.

This capability is included in the March 2017 Public Update available later today. Download the March 2017 Public Update for SharePoint Server 2013 at https://technet.microsoft.com/en-us/library/mt715807(v=office.16).aspx#BKMK_2013.

ssc1

New with the March 2017 Public Update for SharePoint Server 2013 is the option to Create Site Collections in SharePoint Online as illustrated above. When selecting this option any hybrid user that goes to the Self-service Site Creation page (/_layouts/15/scsignup.aspx) will be redirected to SharePoint Online Group creation, and will be able to create a Group and associated Team Site in the Cloud using the new modern group creation flow. Hybrid users are defined through inclusion in one or more audiences as configured when enabling the hybrid sites feature in SharePoint Server 2013. To learn more about hybrid sites and audiences see also https://support.office.com/article/5ff7e56a-7af2-4511-adec-1e043afe244e.

ssc2

For on-premises only users, or those excluded from the hybrid audience as described above, they will still be able to use the existing On-Premise Self-service Site Creation experience.

In addition to the configuration options available directly through SharePoint 2013 Central Administration, there will also be entry points to the configuration page through a one-time Central Administration alert box and from the Hybrid Picker in Office 365.

The cloud is no longer a luxury—it’s central to a mobile, modern workplace—and Office 365 brings the cloud to you, on your terms and across SharePoint and OneDrive we’re constantly working to help you take advantage of the power of Office 365. Kick start the journey to the cloud with hybrid self-service site creation today.

Resources

Learn more about hybrid scenarios across Office 365 at http://hybrid.office.com/.

Download the hybrid scenarios pocket guide with SharePoint and Office 365 at https://go.microsoft.com/fwlink/?linkid=842608.

Get more information on implementing hybrid scenarios with SharePoint and Office 365 at https://support.office.com/en-us/article/SharePoint-Hybrid-4c89a95a-a58c-4fc1-974a-389d4f195383.

FaQ

Q:  Will this feature be available to SharePoint Server 2016?

A:  Yes.  In H2 CY2017 we’ll make available hybrid self-service site creation to customers of SharePoint Server 2016.  In the near term you can continue to deploy the hybrid sites feature as an interim solution.  To learn more about hybrid sites see also https://support.office.com/en-us/article/SharePoint-hybrid-sites-and-search-5ff7e56a-7af2-4511-adec-1e043afe244e.

Standard
Hybrid

Hybrid Scenarios with SharePoint and Office 365 Updates and Recap + Hybrid Taxonomy GA

Cross-posted from my post on the Microsoft Technical Community at https://techcommunity.microsoft.com/t5/SharePoint-Blog/Hybrid-Scenarios-with-SharePoint-and-Office-365-Updates-and/ba-p/47571#M204.

Ubiquitous connectivity, the proliferation of devices – the rise of the cloud.

The cloud has become mainstream and services such as Office 365 are an attractive alternative to on-premises business solutions with SharePoint.  However, for a variety of reasons, you might want to or need to deploy specific solutions in the cloud while still maintaining your on-premises investments.  For some organizations, you may wish to gradually move to cloud using a staged, workload-driven approach.  Hybrid scenarios with Office 365 and SharePoint on-premises allow you to bring the cloud to your business while bringing the business to the cloud.  From on-premises to the cloud and back—your information is where and when you want, at your pace, using the investments you already have. Your existing solutions coexist with the cloud—without the full cost of migration. You can even use Delve and Power BI with on-premises data.

The cloud is no longer a luxury—it’s central to a mobile, modern workplace—and Office 365 brings the cloud to you, on your terms and across SharePoint and OneDrive we’re constantly working to help you take advantage of the power of Office 365.

In November we announced preview availability of two new hybrid scenarios coinciding with Feature Pack 2 for SharePoint Server 2016 – hybrid auditing and hybrid taxonomy..

Hybrid Taxonomy (Generally Available)
Today we’re pleased to announce hybrid taxonomy is generally available.

Taxonomy is key to promoting discoverability and access to the right information at the right time. Hybrid taxonomy in SharePoint Server 2013 and SharePoint Server 2016 allows customers to bring their taxonomy store to Office 365 enabling a single-source for creating and managing Terms, Term Sets and Groups through a single Managed Metadata Service.

Hybrid Auditing (Preview)
Hybrid auditing is a new feature that aims at helping administrators manage their SharePoint infrastructure by giving them access to various reports and dashboards in Office 365. The reports are generated from SharePoint Server 2016 on-premises diagnostic and usage logs.

If you opt in for this service, audit logs get collected and uploaded to Office 365 regularly. From the Office 365 dashboard, you can view auditing and activity reports that show usage and reliability patterns in your SharePoint Server 2016 farm alongside data from your SharePoint Online tenant.

Hybrid auditing will become generally available later this calendar year.

Learn more about hybrid scenarios with Office 365 and SharePoint on-premises at http://hybrid.office.com/.

Resources
Download the hybrid scenarios pocket guide with SharePoint and Office 365 at https://go.microsoft.com/fwlink/?linkid=842608.

Get more information on implementing hybrid scenarios with SharePoint and Office 365 at https://support.office.com/en-us/article/SharePoint-Hybrid-4c89a95a-a58c-4fc1-974a-389d4f195383.

Standard
Hybrid, SharePoint

SharePoint Server 2016 Beta 2 Hybrid Scenarios

SharePoint Server 2016 Beta 2, released on November 18th, 2015, introduces several new hybrid capabilities that drive end-user familiarity and provide further abstraction of Office 365 when coexisting with SharePoint on-premises to include a new hybrid extensible App Launcher and profile redirection.

Extensible App Launcher

The App Launcher is a familiar feature in Office and it’s now been extended to SharePoint Server 2016. The App Launcher provides a common location to discover new apps and navigate SharePoint on-premises and Office 365.

clip_image002

The extensible hybrid app launcher is designed to help you get to your Office 365 apps and services from SharePoint Server 2016 Beta 2.  The extensible App Launcher is enabled when enabling hybrid Team Sites and/or OneDrive for Business, once you enable this feature, you’ll see the Office 365 Delve and Video apps, along with your custom Office 365 tiles, appear in your SharePoint Server 2016 Beta 2 app launcher.

The Extensible Hybrid App Launcher is a SharePoint Server 2016 Beta 2 feature that requires Office 365 functionality which is scheduled to roll out during December 2015 and January 2016.

Learn more about the Extensible App Launcher at http://go.microsoft.com/fwlink/?LinkId=715519.

Profile Redirection

Profile redirection is a component of the hybrid Team Sites feature introduced in SharePoint Server 2013 Service Pack 1.  Profile redirection, in a hybrid Team Sites configuration redirects cloud (hybrid) users to their profile in Office 365 powered by Office Delve ensuring hybrid users have a single place for their profile information.

Learn more about Profile Redirection at http://go.microsoft.com/fwlink/p/?LinkId=708802.

Hybrid Team Sites

Hybrid Team Sites provides a solution to help hybrid users reconcile and rationalize site membership and discovery across SharePoint on-premises and Office 365.  For example, if you're a member of several team sites in your organization, you may want to start following them for easy access.  When you follow a team site, it gets listed on your Sites page.  When you follow sites, you can quickly navigate to libraries on these sites from OneDrive for Business or the Sites tile on-premises or in Office 365.

When a user follows a site, a link to that site is added to the user's Followed Sites list. If you're using both SharePoint Server 2016 Beta 2 and SharePoint Online, your users will have different followed lists for sites in each location. Hybrid sites features consolidates the information from both locations into the SharePoint Online list in Office 365.

Learn more about Team Sites at https://technet.microsoft.com/library/mt346108(v=office.16).aspx.

OneDrive for Business

In SharePoint Server 2016 Beta 2, you can redirect users to OneDrive for Business in Office 365 when they click OneDrive or Sites in the navigation bar. This is known as OneDrive for Business hybrid.

With this feature, no matter where they are, users can quickly access their documents and any information that they choose to sync from their SharePoint sites. This best-of-both-worlds approach lets you keep your key business information in your own environment while allowing users the flexibility to access their documents from anywhere.

With this feature, you can continue to use your on-premises SharePoint farm while providing your users with an easy way to store, share, and collaborate in the cloud with OneDrive for Business in Office 365.

Learn more about hybrid OneDrive for Business at https://technet.microsoft.com/en-us/library/dn627523.aspx.

Search

SharePoint Server 2016 Beta 2 provides two discrete hybrid search scenarios, Cloud Hybrid Search introduced in August 2015 to SharePoint Server 2016 IT Preview and SharePoint Server 2013, in addition to the classic federated hybrid search scenario, introduced in SharePoint Server 2013.

Cloud Hybrid Search

The Cloud Hybrid Search scenario represents the next generation in hybrid search and discovery.  With the cloud hybrid search solution, both your on-premises and Office 365 crawled content is unified in a search index hosted in Office 365.  When users query your search index in Office 365, they get search results from both on-premises and Office 365 content.  The content metadata is encrypted when it’s transferred to the search index in Office 365, so the on-premises content remains secure.  You configure search in Office 365, except for the crawling set-up, which you do on SharePoint Server.

Learn more about cloud hybrid search at http://connect.microsoft.com/office/SelfNomination.aspx?ProgramID=8647&pageType=1.

In SharePoint Server 2016 Beta 2 a Cloud Search Service Application can be created in SharePoint Central Administration; however, onboarding requires running the onboarding script that can be downloaded via link above. 

Federated Hybrid Search

Federated hybrid search is a hybrid search scenario in which a query issued by a user is federated or distributed across on-premises and Office 365 returning a set of results from each location as discrete entities.  In a federated hybrid search scenario on-premises crawled content is stored on-premises in the search index and Office 365 content in the search index in Office 365 with no affinity between the two data sets.  Federated hybrid search can be configured in inbound, outbound, or bi-directional hybrid topologies.

Outbound

User searches from the SharePoint Server 2013 Search Center display hybrid results. This is called outbound hybrid search. For information about how to set up outbound hybrid search, see Display hybrid search results in SharePoint Server 2013.

Inbound

User searches from the SharePoint Online Search Center display hybrid results. This is called inbound hybrid search. For information about how to set up inbound hybrid search, see Display hybrid search results in SharePoint Online.

Hybrid Scenario Picker

The hybrid scenario picker is a new feature in Office 365 that simplifies the configuration and deployment of hybrid capabilities with SharePoint Server 2013 and SharePoint Server 2016.  You can use the scenario picker wizard to redirect OneDrive for Business to SharePoint Online, and/or to make a Server-to-Server (S2S)/OAuth connection for your SharePoint Hybrid features.

Learn more about the Hybrid Scenario Picker at http://go.microsoft.com/fwlink/?LinkID=620229&clcid=0x409.

Extranet Sites 

An extranet site in SharePoint is a site that organizations create to let external users have access to relevant content and to collaborate with them. Extranet sites allow a way for partners to securely do business with your organization. The content for your partner is kept in one place and they have only the content and access they need. They don’t need to email the documents back and forth or use some tools that are not sanctioned by IT.

Traditionally, deploying a SharePoint on-premisesextranet site involves complex configuration to establish security measures and governance, including granting access inside the corporate firewall, and expensive initial and on-going cost.

But with O365 SharePoint Hybrid extranet, partners connect directly to a members-only site in Office 365, without access to the corporate on-premises environment or any other Office 365 site. Office 365 Extranet sites can be accessed anywhere.

Learn more about hybrid Office 365 Extranets at  http://go.microsoft.com/fwlink/?LinkID=537696&clcid=0x409.

Document Collaboration

Recently a new attachment option has been made available in Office 365. In Exchange 2016, this option, known as document collaboration, allows on-premises users to integrate attachments stored on OneDrive for Business directly in their Outlook on the web clients.

Learn more about Document Collaboration at http://go.microsoft.com/fwlink/?LinkId=715521.

Get Started with SharePoint Hybrid

SharePoint Hybrid is about connecting best of both worlds, on-premises and Cloud, together and achieve business values through hybrid pillars.

A hybrid solution can help your company get started in the cloud, taking a first step to explore the cloud functionality at own your pace. A hybrid environment enables enterprise users to be connected from almost anywhere to the resources and content they need.

Learn more about hybrid SharePoint at http://hybrid.office.com/.

Standard
Hybrid

Simplifying Hybrid Configuration with the new Hybrid Scenario Picker

This month we continued to invest in simplifying the Office 365 and SharePoint 2013 hybrid experience with the new hybrid scenario picker available in the Office 365 Administration Center.

Overview

The hybrid scenario picker is designed to help customers get up and running quickly with in-market and future hybrid scenarios by providing quick access to hybrid scenarios such as OneDrive for Business and SharePoint Sites in addition to programmatically configuring hybrid prerequisites to include Server-to-Server (S2s) and OAuth connections.

H1

Scenarios

The current hybrid scenario picker experience provides access to two (2) core scenarios supported with SharePoint Server 2013 and the upcoming release of SharePoint Server 2016 Preview.

H2

SharePoint Hybrid OneDrive for Business – The Hybrid OneDrive option redirects your on-premises My Sites/OneDrive host to SharePoint Online OneDrive for Business. Once the wizard completes, any click of the OneDrive link from on-premises will redirect to OneDrive in the Cloud. The redirection is complete and users may begin moving or syncing files to the Cloud for storage, right away.  The wizard also configures a sever-to-server (S2S/OAuth) connection between SharePoint Server on-premises and SharePoint Online.

SharePoint Hybrid Site Features – The Hybrid SharePoint Sites option configures a server-to-server (S2S/OAuth) connection that allows you to join features of your team site to your SharePoint Online site collection in Office 365.  OneDrive for Business redirection is also configured when you click this option. Note that, depending on what hybrid features you want to use, there may be other steps that you need to complete when this wizard finishes.  For example, if you want to configure SharePoint Server search as a hybrid of SharePoint Online and SharePoint Server on-premises.

Prerequisites

To successfully configure a hybrid Office 365 and SharePoint 2013 experience using the hybrid scenario picker your SharePoint Server 2013 farm should have the August PU installed, ports 80 and 443 should be open for outbound connections, and users synchronized with Office 365 using Azure Active Directory Sync (AAD Sync).

Resources

To learn more about hybrid Office 365 and SharePoint scenarios see also https://technet.microsoft.com/en-us/library/jj838715.aspx.

Standard
Administration, SharePoint

SharePoint IT…evolving?

The English philosopher Alan Watts once said “The only way to make sense out of change is to plunge into it, move with it, and join the dance”.

A recent #CollabTalk topic was that of the changing role of SharePoint IT…as the cloud becomes mainstream, this conversation will inevitably thrive as a broader topic that transcends SharePoint.

And while change may be to exist, opportunity continues to rise – the cloud has given way to capabilities previous impossible behind the firewall, from predictive analytics to machine learning, to infinite storage, and on-demand access to content and conversations.

For IT, the cloud is oft perceived as a disruptive force as it’s enabled both business and individuals to secure technology on their own, ushering in the BYOD era – and while disruption can be real or perceived, there’s opportunity for IT to become an enabler.  Though the pressures exist that ask IT to do more, to drive business process, reduce cost, advance innovation, and deliver new, compelling user experiences… the cloud uniquely positions IT to meet those demands.

The role of IT has largely been based on a reactive relationship to the environments which they support, the opportunity in this transition to the cloud enables IT to become a proactive force, a value added service broker.

When we launched SharePoint Server 2013 in October of 2012 we had a vision of which the cloud and on-premises would converge – through parity and through unique technology investments that differentiate SharePoint from other collaborative platforms, hybrid is representative of those early investments.  As we moved through 2013 we delivered a number of cumulative updates and introduced new ways to consume SharePoint, namely in Windows Azure. Finally in early 2014 just prior to the 2014 SharePoint Conference we shipped Service Pack 1.  Throughout the lifecycle of SharePoint, we’ve continued to explore ways we can support IT through this transition, to enabling OneDrive for Business in Office 365 and Yammer for SharePoint on-premises, to improving the hybrid experience.

SharePoint on-premises provides a valuable experience that is defined by the sum of its parts whereas in the cloud, SharePoint isn’t delivered as much as a platform, but through its unique capabilities.  On-premises search experiences are defined by the OOTB search service, in the cloud by Office Delve, social is defined by the Newsfeed, in the cloud, by Yammer, collaboration and mobility is defined in Team Sites, Device Channels, etc., in the cloud, by OneDrive for Business…

So has IT changed?  Absolutely, but for the better…with new opportunities IT becomes an extension of the business, driving and delivering strategy and pulling together experiences within and beyond the firewall.

Succeeding with the cloud is understanding where it can add value to existing capabilities such as enabling mobility and anytime, anywhere access while working with familiar IT controls, or extending your datacenter with Microsoft Azure, extending your platform with SharePoint in Microsoft Azure, and extending your workloads with Office 365.

As Albert Einstein said “Strive not to be a success, but rather to be of value”.

Learn more at http://technet.microsoft.com/en-us/library/jj838715(v=office.15).aspx.  These resources provide a roadmap for exploring, planning, installing, and configuring SharePoint Server 2013 and SharePoint Online hybrid environments.

Standard
Administration, SharePoint

Implementing Azure Blob Storage (ABS) with SQL Server 2014 and SharePoint 2013 [Updated]

Overview

NOTE (8/26/2014)

With any solution that externalizes the unstructured content with SharePoint you need to understand the limitations and optimal use of those solutions as documented at http://technet.microsoft.com/en-us/library/ff628583(v=office.15).aspx to include related latency and performance requirements.

With any application organizations face consistent key challenges such as high efficiency and business value, complex configuration, and low total cost of ownership.  Extending applications to the cloud in hybrid scenarios addresses many of these challenges, whether distributing SharePoint content across on-premises and Office 365 while leveraging search as a service (hybrid search) or externalizing data, extending it to the cloud with Remote Blob Storage or related technologies.

SQL Server 2014 and Windows Azure Blob Storage provide a unique solution that balances the needs of IT with those of the business – SQL Server Data Files in Windows Azure which allows you to create a database in SQL Server running in on-premises or in a virtual machine in Windows Azure with a dedicated storage location for your data in Windows Azure Blob Storage.

Picture1

This enhancement especially simplifies to move databases between machines by using detach and attach operations. In addition, it provides an alternative storage location for your database backup files by allowing you to restore from or to Windows Azure Storage. Therefore, it enables several hybrid solutions by providing several benefits for data virtualization, data movement, security and availability, and any easy low costs and maintenance for high-availability and elastic scaling.

Prerequisites

SQL Server 2014 on-premises or as a Windows Azure Virtual Machine

Storage Account and Container in Windows Azure

When using SQL Server Data Files in Windows Azure feature, you need to create a storage account and a container in Windows Azure, create a SQL Server credential, which includes information on the policy of the container as well as a Shared Access Signature that is necessary to access the container.

Getting Started

Create a Storage Account

To store files and data in the Blob, Table, Queue, and File services in Azure, you must create a storage account in the geographic region where you want to store the data.

For step by step instructions on how to create a Storage Account using the Windows Azure Management Portal see http://azure.microsoft.com/en-us/documentation/articles/storage-create-storage-account/.

image

Create a Container

All storage blobs reside in a container.   To create a container:

Sign in to the Management Portal.

Click Storage from the list of available options and select the Storage Account created in the previous steps.

Click CONTAINERS from the list of available options.

image

On the CONTAINERS dialog click + Add and specify the name for the new container.

image 

NOTE

Keep the default access level ‘Private’.

By default, the container is private and can be accessed only by the account owner. To allow public read access to the blobs in the container, but not the container properties and metadata, use the "Public Blob" option. To allow full public read access for the container and blobs, use the "Public Container" option.

The following steps assume that a Windows Azure Storage container has been created, and a policy has been created with read, write, list, rights. Creating a policy on a container generates a SAS key which is safe to keep unencrypted in memory and needed by SQL Server to access the blob files in the container.

Create a Credential

Creating a credential creates a record that contains the authentication information that is required to connect to a resource outside SQL Server. (such as Azure Blob Store).  To create a credential for Azure Blob Store requires a Windows Azure Store Container and a policy to allow read, write, and list rights.  Creating a policy generates a SAS key which SQL Server uses to access the blobs in the container.

Syntax

CREATE CRENDENTIAL [Container Url] — Specifies the name of the credential being created, I.e. the Windows Azure Storage Container

WITH IDENTITY = ‘SHARED ACCESS SIGNATURE’ — Specifies the name of the account to be used when connecting outside the server, I.e. when used with a Windows Azure Storage Container this value is always ‘SHARED ACCESS SIGNATURE’.  A Shared Access Signature is a URI that grants restricted access rights to containers, blobs, queues, and tables for a specific time interval (see example below).

For information on creating and using Shared Access Signatures see http://msdn.microsoft.com/en-us/library/azure/jj721951.aspx.

SECRET = ‘Secret’ — Specifies the secret required for outgoing authentication.   In this scenario the SECRET represents the Shared Access Signature associated with the policy created on the container (see example below).

Example

USE master
CREATE CREDENTIAL [https://sqlcloud.blob.core.windows.net/data%5D
WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
SECRET = 'sr=c&se=2014-08-25T18%3B34%3B29Z&sp=rwl&sig=wJripFB9nq%2FrwlARE11TYS1OccKpFrpn6y3QuRS%2Fv4o%3D'

To view the credential created in the steps above use:

SELECT * FROM sys.credentials

The sys.credentials Security Catalog View returns one row for each stored credential which includes:

name = Name of the credential. Is unique in the server.

credential_identity = Name of the identity to use.

create_date = Time at which the credential was created.

modify_date = Time at which the credential was last modified.

target_type = Type of credential. Returns NULL for traditional credentials such as SHARED ACCESS SIGNATURE.

target_id = ID of the object that the credential is mapped to. Returns 0 for traditional credentials.

image

Create a Database

Creating a database does not differ significantly from creating a database in a traditional on-premises SQL Server storage scenario using the CREATE DATABASE statement.

Syntax

CREATE DATABASE [Name] — Is the name of the new database.

ON ( NAME = [Database Name], FILENAME = [Data File Path and File Name] ) — Specifies that the disk files used to store the data sections of the database, data files, are explicitly defined.

LOG ON ( Name = [Log Name], FILENAME = [Log File Path and File Name] ) Specifies that the disk files used to store the database log, log files, are explicitly defined.

Example

CREATE DATABASE WSS_Content
ON ( NAME = WSS_Content, FILENAME = 'https://sqlcloud.blob.core.windows.net/data/WSS_Content.mdf' )
LOG ON ( NAME = WSS_Content_Log, FILENAME = 'https://sqlcloud.blob.core.windows.net/data/WSS_Content.ldf' )

Validate Database Creation

To validate the database and related files were created successfully in the container select Connect in SQL Server Management Studio and choose Windows Azure from the list of available options.  Specify the name of the storage account associated with the container and provide the related access key to access the container.

image

Add Database(s) to SharePoint

To add the database use the Mount-SPContentDatabase cmdlet which attaches an existing content database to the farm.

Syntax

Mount-SPContentDatabase

-Name Specifies the existing content database to attach to the farm.

-DatabaseServer Specifies the name of the host server for the content database specified in the Name parameter.

-WebApplication Attaches the content database to the specified SharePoint web application.

Example

Mount-SPContentDatabase “WSS_Content” –DatabaseServer CP-SQ-01 –WebApplication http://sharepoint.wbaer.com.co

Summary

SQL Server Data Files in Windows Azure simplifies migration processes by moving one database at a time between machines on-premises as well as between on-premises and cloud environments without any application changes and provides near limitless storage without the overhead of managing storage.

Standard
Hybrid, SharePoint

SharePoint 2013 and Office 365 Hybrid

The French philosopher, Henry Bergson, once said “to exist is to change, to change is to mature, to mature is to go on creating oneself endlessly.” While the Nobel Prize winner wasn’t talking about the software and services world, the thought is extremely applicable to technology- from development to administration to use. The adoption of, and change to, cloud computing is maturing at a rapid rate…but the move needs to be thoughtful.

At Microsoft we are truly embracing this change through our cloud first/mobile first mantra and we have seen customer interest grow for all of our maturing cloud services, in a very significant way- from IaaS capabilities in Microsoft Azure, to gaming and entertainment consumption in XBOX Live to our productivity and collaboration solutions for Office 365. In all cases, customers love the time to value, cadence of new and helpful features and predictive costs that the cloud computing offers.

However, we also know that the move to cloud doesn’t happen all at once. In Office 365, we have seen incredible interest and growth for all of our services, including SharePoint Online. To that end, we absolutely recognize customers need to balance their desire to adopt SharePoint Online, while still maintaining existing, on-premises, SharePoint Server investments until the time when they can be migrated to the cloud.

For those customers ready to thoughtfully embrace the change to cloud, we are committed to helping you with our hybrid models and tools so you can leverage the Microsoft Cloud to change your business endlessly. We believe the future of work is how we build relationships, share information, and respond to conditions that can change at a moment’s notice, Office 365 is the cornerstone of our response, and with our current and future investments we’re helping to bring you there with as little friction as possible.

For more information and to understand what hybrid scenarios can do for your business see the following resources:

Check out new downloadable content you can share with your organization at http://technet.microsoft.com/en-us/library/dn769084(v=office.15).aspx

Learn more about Hybrid Models with SharePoint and Office 365 [http://technet.microsoft.com/en-us/library/jj838715(v=office.15).aspx]

Download Hybrid SharePoint 2013 Resources [http://technet.microsoft.com/en-us/library/jj838715(v=office.15).aspx]

Check back often as we continue to innovate on our hybrid vision to help you realize the best of on-premises and the cloud.

Standard