Administration, Events, Hybrid, OneDrive for Business, SharePoint

Ignite 2017 Pre-Day Training – SharePoint and Office 365 Hybrid Scenarios

Join myself, Neil Hodgkinson, Spence Harbar, Bob Fox, and other industry experts for a Microsoft Ignite pre-day training on implementing hybrid scenarios with SharePoint and Office 365.

Cloud computing has become a popular way to reduce capital and operational expenditures, renew IT innovation, and gain the advantage of more rapid software delivery to meet the needs of business. However, compliance, data sovereignty, sensitivity concerns, or a significant investment in customization may limit your organization’s ability to take advantage of this. Today you can maximize your on-premises investment by upgrading to SharePoint Server 2016 and using hybrid scenarios in Office 365 to seamlessly leverage the cloud. This pre-day workshop is designed to give you the deep technical knowledge to deploy SharePoint Server 2016 as well as design and implement the latest hybrid scenarios including search, auditing, taxonomy and more.

Attendees will receive instructor led training on best practices for implementing a variety of hybrid scenarios and workloads, training materials, to include documentation and presentations and a each, a dedicated lab environment including a SharePoint Server 2016 farm and an Office 365 Tenant that can be used to complete hands on labs during and after the event.

Space is limited, register today https://www.microsoft.com/en-us/ignite/agenda.

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
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
Hybrid, SharePoint

One-Way Outbound Hybrid Search Step-by-Step and OneDrive for Business

Recently we introduced a number of new coexistence scenarios in Service Pack 1 including redirection of OneDrive for Business and Yammer.  Redirection of OneDrive for Business enables IT to provision cloud storage for users OneDrive for Business document libraries; however, in a hybrid scenario the content in that storage should be discoverable both on-premises and online.  The most common configuration to support OneDrive for Business redirection is an outbound search topology where users can return results from both on-premises and online within the on-premises search portal.

NOTE Office 365 returns only local results.

The steps below assume a hybrid identity infrastructure is configured for the target environment.  The hybrid identity infrastructure can be:

  1. Cloud Identity – suitable for small organizations with up to 50 users, no affinity to on-premises Active Directory identity.
  2. DirSync – suitable for larger organizations, provides a consistent authentication experience when combined with Password Sync.
  3. AD FS / SSO – suitable for larger organizations planning to deploy complex hybrid workloads to include BCS, bidirectional search, etc.

See also Configure identity management for a hybrid topology in SharePoint Server 2013 [http://technet.microsoft.com/en-us/library/dn197169(v=office.15).aspx

Install Prerequisites

On one or more Web servers install the following prerequisite software:

  1. Microsoft Online Services Sign-In Assistant for IT Professionals RTW (msoidcli_64bit.msi)
  2. Windows Azure Active Directory Module for Windows PowerShell (64-bit version)
  3. SharePoint Online Management Shell (sharepointonlinemanagementshell_64bit.msi)

Configure Server-To-Server Authentication Between SharePoint Server 2013 and Office 365

Server-To-Server authentication in hybrid environments between SharePoint Server 2013 and Office 365 creates a trust relationship between SharePoint Server 2013 and a SharePoint Online Tenant.  In this scenario Windows Azure Active Directory provides the trusted signing service.

Certificate Management

The Security Token Service (STS) is the service component that builds, signs, and issues security tokens according to the WS-Trust and WS-Federation protocols. Replacing the STS certificate in SharePoint Server 2013 is necessary to establish trust between the Security Token Service of SharePoint Server 2013 and the SharePoint Online Tenant.  Replacing the STS certificate enables the STS Service and Windows Azure Active Directory to sign security tokens for authenticated users.

NOTE The steps below should be used in pilot/development/lab environments.  A certificate provided by a known CA should be used in production environments.

Create a Self-Signed Certificate

Open Internet Information Services (IIS Manager) on Web server:

  1. Click Start > Administrative Tools > Internet Information Services (IIS Manager)
  2. Click the server name in the Connections pane.
  3. Double-click Server Certificates in the Details pane.
  4. Click Create Self-Signed Certificates in the Actions pane.
  5. On the Create Self-Signed Certificate Dialog provide a name for the certificate under Specify a friendly name for the certificate: (I.e. STS) and click OK to create the certificate.

image

Export a PFX Certificate

A Personal Information Exchange certificate that is issued by a signing authority and verifies the authenticity and security of the hosted service (can be a self-signed certificate for testing purposes). The format of this certificate uses a .pfx extension.

Open Internet Information Services (IIS Manager) on a Web server:

  1. Click Start > Administrative Tools > Internet Information Services (IIS Manager)
  2. Click the server name in the Connections pane.
  3. Double-click Server Certificates in the Details pane.
  4. Right-click the Self-Signed Certificate created in the previous step and select Export from the list of available options.

Export a CER Certificate

In Internet Information Services (IIS Manager) select the Self-Signed Certificate created in the previous steps.

  1. Click Start > Administrative Tools > Internet Information Services (IIS Manager)
  2. Click the server name in the Connections pane.
  3. Double-click Server Certificates in the Details pane.
  4. Right-click the Self-Signed Certificate created in the previous step and select View from the list of available options.
  5. Click Copy to File on the Details tab and then click Next.
  6. On the Export Private Key page, click Next.
  7. For Export File Format page, choose Base-64 encoded X.509 (.CER). Click Next.
  8. For Export Certificate type a path and file name for the .cer file. Click Next.
  9. Click Finish, and then click OK twice.

Server-To-Server Authentication

Server-to-server authentication allows for servers that are capable of server-to-server authentication to access and request resources from one another on behalf of users. Servers that are capable of server-to-server authentication run SharePoint 2013, Exchange Server 2013, Lync Server 2013, Azure Workflow Service, or other software that supports the Microsoft server-to-server protocol.

Configure Server-To-Server Authentication

Configuring server-to-server is necessary to service incoming requests from another SharePoint 2013 server farm or service where the primary SharePoint 2013 server farm trusts the send farm.  The following steps use the New-SPTrustedSecurityTokenIssuer CmdLet to configure the trust relationship by providing the JSON metadata endpoint of the sending farm.

Populate Common Variables

Open the SharePoint 2013 Management Shell:

NOTE The remaining steps in this article will be executed within this SharePoint 2013 Management Shell dialog.

  1. Click Start > SharePoint 2013 Management Shell and at the PS prompt enter:

$PFXCertificate = “<Drive:Path>”

$CERCertificate = “<Drive:Path>”

$PFXCertificatePassword = “<password>”

$RootDomain = *<Root FQDN>.com (I.e. *.corp.contoso.com)

NOTE In this example the domain FQDN is wbaer.com.co (see below).

image

$RootSite = Get-SPSite <Top-Level Site Collection> (I.e. http://sharepoint.corp.contoso.com)

$Site = Get-SPSite $RootSite

$SPOAppId = "00000003-0000-0ff1-ce00-000000000000"

$SPOContextId = (Get-MsolCompanyInformation).ObjectID

Update Security Token Service Certificate

Updating the Security Token Service Certificate requires initializing a new instance of the X509Certificate2 class using a certificate file name and a password used to access the certificate in addition to the X.509 format version of the certificate prior to importing the signing certificate.

In the SharePoint 2013 Management Shell at the C> prompt enter:

$STSCertificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PFXCertificate, $PFXCertificatePassword, 20

Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $STSCertificate

NOTE Enter [Y]es when prompted to replace the certificate.

In order to properly update the STS with the new certificate in the command prompt enter:

IISRESET and allow the service to restart

NET STOP SPTimerV4 and allow the Timer Service to stop

NET START SPTimerV4 and allow the Timer Service to start

Convert Certificates to Base64

$STSCertificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 -ArgumentList $PFXCertificate, $PFXCertificatePassword

$PFXCertificateBin = $STSCertificate.GetRawCertData()

$Certificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2

$Certificate.Import($CERCertificate)

$CERCertificateBin = $cerCertificate.GetRawCertData()

$CredentialValue = [System.Convert]::ToBase64String($CERCertificateBin)

Connect to Office 365

Enable-PSRemoting

Enter [A] Yes to All when prompted.

New-PSSession

$Credentials = Get-Credential

Connect-MsolService -Credential $Credentials

Import MS Online Modules

Import-Module MSOnline -force
Import-Module MSOnlineExtended -force

Register the SharePoint 2013 STS as the Office 365 Service Principal

New-MsolServicePrincipalCredential -AppPrincipalId $SPOAppId -Type asymmetric -Usage Verify -Value $CredentialValue

$SharePoint = Get-MsolServicePrincipal -AppPrincipalId $SPOAppId

$ServicePrincipalName = $SharePoint.ServicePrincipalNames

$ServicePrincipalName.Add("$SPOAppId/$RootDomain")

Set-MsolServicePrincipal -AppPrincipalId $SPOAppId -ServicePrincipalNames $ServicePrincipalName

$SPOContextId = (Get-MsolCompanyInformation).ObjectID

$SPOAppPrincipalId = (Get-MsolServicePrincipal -ServicePrincipalName $SPOAppId).ObjectID

$SPONameIdentifier = $APOAppPrincipalId@$SPOContextId

Establish SharePoint 2013 Trust with ACS

Windows Azure Active Directory Access Control is a cloud-based service that provides an easy way of authenticating and authorizing users to gain access to your web applications and services while allowing the features of authentication and authorization to be factored out of your code.

In a hybrid topology rather than implement an authentication system with user accounts specific to the application, ACS orchestrates the authentication and authorization of users.

$AppPrincipal = Register-SPAppPrincipal -site $Site.rootweb -nameIdentifier $SPONameIdentifier -displayName "SharePoint Online"

Set-SPAuthenticationRealm -realm $SPOContextId

New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -MetadataServiceEndpointUri "https://accounts.accesscontrol.windows.net/metadata/json/1/&quot; -DefaultProxyGroup

New-SPTrustedSecurityTokenIssuer -MetadataEndpoint "https://accounts.accesscontrol.windows.net/metadata/json/1/&quot; -IsTrustBroker -Name "ACS"

Confirm Trust Relationship Configuration

Open SharePoint 2013 Central Administration to confirm Trust is configured:

  1. Click Start > SharePoint 2013 Central Administration and select Security.
  2. Select Manage trust from the list of available options and confirm two (2) ACS_<GUID> entries exist.

image

    Configure Query Results and Rules

    In order to surface content stored in SharePoint Online / OneDrive for Business a new Results Source and Query Rule are required on the SharePoint Server 2013 on-premises environment.  Optionally, where only OneDrive for Business is cloud-enabled, a new search vertical may be sufficient; however, in the event additional workloads to include general collaboration will be considered for the cloud, a base Results Source / Query Rule should be configured to aggregate results across all site collections (including OneDrive for Business) where a OneDrive for Business Result Type can be further configured for refinement.

    Create Results Source

    Result sources in SharePoint limit searches to certain content or to a subset of search results. SharePoint Server 2013 provides 16 pre-defined result sources. The pre-configured default result source is Local SharePoint Results.  In these steps a new Results Source will be created for Remote SharePoint in order to discover content stored in SharePoint Online / OneDrive for Business.

    Open SharePoint 2013 Central Administration:

    1. Click Start > SharePoint 2013 Central Administration and select Application Management.
    2. Select Manage service applications from the list of available options.
    3. Select the Search Service Application from the list of available Service Applications.
    4. Select Result Sources under Queries and Results and then click New Result Source on the Manage Result Sources page.
    5. On the Add Results Source page provide a name for the Result Source in the Name field (I.e. SharePoint Online).
    6. Select Remote SharePoint under Protocol.
    7. Provide the Url of the root Site Collection in SharePoint Online under Remote Service Url (I.e. http://contoso.sharepoint.com)
    8. Select SharePoint Search Results under Type.
    9. Under Query Transformation select or modify the existing method (the default is {searchTerms}.
    10. Select Default Authentication under Credentials Section.
    11. Click OK to save the Results Source created above.

    image

      Create Query Rule

      Query Rules in SharePoint help searches respond to the intent of users through conditions and correlated actions.  For example, when a query meets the conditions in a query rule, the search system performs the actions specified in the rule to improve the relevance of the search results.

      1. On the Search Administration page select Query Rules under Queries and Results.
      2. On the Manage Query Rules page select the Results Source created in the previous steps.
      3. Click New Query Rule and provide a Rule Name (I.e SharePoint Online Results).
      4. Expand the Context section:
        1. Select All sources under Query is performed on these sources.
        2. Select All categories under Query is performed from these categories.
        3. Select All user segments under Query is performed by these user segments.
      5. On the Query Conditions section click Remote Condition  to allow the query to fire for any query text.
      6. On the Actions section click Add Result Block.
        1. Select the Results Source (SharePoint Online) under Search this Source.
      7. Click Save to save the Query Rule.

      NOTE This query rule will apply to all sites. To make one for just a specific site, use the query rules page in its Site Settings

      Validate Results Source (Central Administration)

      1. To validate the new Results Source in Search Administration select Result Sources under Queries and Results.
      2. Select the Result Source created in the previous steps and click Test Source.
      3. In the Test Result Source Dialog verify the Test details: results reports Succeeded.

      Validate Results Source (Search Center)

      1. Open the Search Center used by the Search Service Application and query a term used across SharePoint Server 2013 and SharePoint Online.
        1. Validate the results are retrieved from local results set.
      2. Under Results found in <local> select Everything.
        1. Validate the upper Results Block contains results from SharePoint Online and the lower Results Block, local results.

      image

      Conclusion

      Combining an outbound hybrid search topology with OneDrive for Business redirection in Service Pack 1 provides on-premises users of SharePoint Server 2013 visibility to content stored in OneDrive for Business libraries in Office 365 improving discovery and manageability of cloud content.

      Implementing DirSync with Password Sync reduces overall complexity and provides an integrated authentication experience to support rapid provisioning of cloud storage.

      Resources

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

      Display hybrid search results in SharePoint Server 2013 [http://technet.microsoft.com/en-us/library/dn197173(v=office.15).aspx]

      Standard
      Hybrid, SharePoint

      OneDrive for Business Redirection to Office 365 Overview

      At the 2014 SharePoint Conference we announced the new OneDrive for Business SKU in addition to changes in Service Pack 1 functionality that enable IT administrators to selectively redirect their users to OneDrive for Business in Office 365 from SharePoint Server 2013.

      Planning

      The initial prerequisite steps to implementing OneDrive for Business redirection to Office 365 in Service Pack 1 is choosing the most effective identity management/federation options to suit your business needs.  At minimum cloud identity is required to enable redirection to OneDrive for Business in Office 365 or otherwise organizations seeking a more integrated, seamless experience should consider Directory Synchronization with Password Synchronization or ADFS / SSO for integrated authentication and authorization experiences.

      Identity Management

      A properly planned identity management solution is the basis for any hybrid topology and the key to the user experience.

      Cloud Identity

      Cloud identities provide the most rapid solution to provisioning users in Office 365 and is based on a separate discrete set of credentials established in Windows Azure Active Directory; however, no correlation exists between the cloud identity and the organizations’ identity primary identity provider (I.e. AD DS).
      Cloud identity provides a rapid, easy to configure scenario for smaller organizations as businesses can quickly establish, manage, and authenticate users with no change to their existing identity management systems or practices.  In a cloud identity scenario, users are discretely managed through a Web portal and Windows Azure Active Directory in the Microsoft cloud.

      Advantages

      • Requires no additional hardware or change to existing identity management infrastructure
      • Simple management and control of user identity – suitable for organizations with 0-50 users

      Disadvantages

      • Identity and authentication are management completely in the cloud without affinity to an on-premises AD store
      • Discrete credentials across SharePoint 2013 and Office 365
      • Disconnected user experiences
      • Cannot be combined / used with hybrid SharePoint 2013 / Office 365 hybrid topologies

      Directory Synchronization with Password Sync

      Directory Synchronization enables an organization with an established on-premises Active Directory environment to leverage their existing on-premises and user and group accounts in Office 365 reducing overall operational costs providing easier user access to cloud services such as OneDrive for Business.  Directory Synchronization continously synchronizes on-premises user and group accounts with Windows Azure Active Directory.  Combining Directory Synchronization with Password Sync synchronizes user passwords in addition to user and group accounts to Windows Azure Active Directory allowing users to log into cloud services using the same credentials they use to log into their corporate network.

      Advantages

      • Requires no additional hardware or change to existing identity management infrastructure
      • Eliminates the need to manually manage user and group accounts in Windows Azure Active Directory
      • Enables a integrated user authentication experience across on-premises and cloud services

      Disadvantages

      • Somewhat disconnected user experience (users are required to log into cloud services)
      • If a user is in the scope of the password sync feature, the cloud account password is set to "Never Expire". This means that it is possible for a user's password to expire in the on-premises environment, but they can continue to log into cloud services using this expired password.
      • Users are authenticated against cloud services as opposed to on-premises Active Directory

      Resources

      Directory Synchronization Roadmap [http://technet.microsoft.com/en-us/library/hh967642.aspx]
      Directory Sync with Password Sync Scenario [http://technet.microsoft.com/en-us/library/dn441214.aspx]
      Identity and Authentication in Cloud (Poster) [http://www.microsoft.com/en-us/download/details.aspx?id=38193]

      Active Directory Federation Services and Single Sign-On

      Active Directory Federation Services (AD FS) makes it possible for local and federated users to use claims-based single sign-on (SSO) to Web sites and services including cloud services such as Office 365. Organizations can use AD FS to enable your organization to collaborate securely across Active Directory domains with other external organizations by using identity federation reducing the need for duplicate accounts, management of multiple logons, and other credential management issues that can occur when establishing cross-organizational trusts.

      Advantages

      • Complete SSO experience with minimal to no credential prompts
      • Improved security over Directory Synchronizations (users are authenticated against on-premises Active Directory)
      • Required for complex hybrid scenarios

      Disadvantages

      • Additional infrastructure required (FS)
      • Added operational complexity

      Resources

      Office 365 Single Sign-On with AD FS 2.0 Whitepaper [http://www.microsoft.com/en-us/download/details.aspx?id=28971]

      Redirection

      OneDrive for Business

      OneDrive for Business redirection in Service Pack 1 allows IT administrators to selectively determine which users should be redirected to Office 365 for OneDrive for Business through Audiences.

      Audiences are part of a User Profile service application that enables organizations to target content to users based on their job or task. Audiences can be defined by one or a combination of the following items:

      • Membership in a distribution list

      • Membership in a Windows security group

      • Location in organizational reporting structure

      • By public properties in user profiles

      For example, an organization may elect to redirect a subset of their users by creating a Security Group (OneDrive Cloud Users) that establishes the basis for an Audience in the User Profile Service Application.

      Sites Page

      In addition to redirection of OneDrive for Business, IT administrators can additionally configure redirection of users Sites page to Office 365.  When redirection of the Sites page is configured users who are redirected to Office 365 will see followed sites and recommendations based on their Office 365 profile – these users will not see sites and recommendations based on on-premises SharePoint Server 2013.

      Resources

      Plan for OneDrive for Business in SharePoint Server 2013 [http://technet.microsoft.com/en-us/library/dn232145(v=office.15).aspx]
      Redirect users to Office 365 with OneDrive for Business [http://technet.microsoft.com/en-us/library/dn627524(v=office.15).aspx]
      How to redirect users to Office 365 with OneDrive for Business [http://technet.microsoft.com/en-us/library/dn627525(v=office.15).aspx]
      Redirect users to Office 365 with OneDrive for Business: Scenario Overview [http://technet.microsoft.com/en-us/library/dn627523(v=office.15).aspx]
      Overview of OneDrive for Business in SharePoint Server 2013 [http://technet.microsoft.com/en-us/library/dn167720(v=office.15).aspx]

      Discovery

      In addition to configuring user redirection, IT administrators should also consider the implications of content discovery across SharePoint Server 2013 on-premises and Office 365.

      A SharePoint 2013 / Office 365 hybrid topology supports one of three possible hybrid search topologies 1) one-way inbound, 2) one-way outbound, and 3) two-way.  Each search topology requires careful consideration and planning and they provide unique user experiences that should be evaluated against user needs and use case scenarios.

      Outbound Topology

      A one-way outbound hybrid authentication topology enables hybrid service integration in a single direction. In a one-way outbound hybrid topology SharePoint Server 2013 on-premises consumes content and resources from Office 365. For example, search can be configured to allow federated users to see both local and remote search results in a SharePoint Server 2013 search portal.  An outbound search topology is implemented where SharePoint Online results should appear in a separate result block in SharePoint Server 2013 on-premises.  Outbound topologies are the most effective for use with OneDrive for Business redirection as they require minimal configuration and infrastructure requirements.

      Resources

      Plan a one-way outbound hybrid topology [http://technet.microsoft.com/en-us/library/dn607307(v=office.15).aspx]

      Inbound Topology

      A one-way inbound hybrid authentication topology enables hybrid service integration in a single direction. In a one-way inbound hybrid topology Office 365 consumes content and resources from SharePoint Server 2013 on-premises. For example, search can be configured to allow federated users to see both local and remote search results in an Office 365 search portal.  An inbound search topology is implemented where SharePoint Server 2013 on-premises results should appear in a separate result block in SharePoint Online.  Inbound topologies, unlike outbound topologies, require additional infrastructure (reverse proxy device) and are least commonly implemented when redirecting OneDrive for Business to Office 365 as both local and remote results are available only in SharePoint Online.

      Resources

      Plan a one-way inbound hybrid topology [http://technet.microsoft.com/en-us/library/dn607316(v=office.15).aspx]

      Bidirectional Topology

      A two-way topology enables bidirectional hybrid service integration between SharePoint Server 2013 on-premises and Office 365. For example, search can be configured to allow federated users to see both local and remote search results in either SharePoint Server 2013 on-premises or SharePoint Online search portals.  Bidirectional topologies, like inbound topologies, require additional infrastructure (reverse proxy device) in addition to VPN and/or DirectAccess to support display of results across SharePoint Server 2013 on-premises and SharePoint Online.

      Resources

      Plan a two-way hybrid topology [http://technet.microsoft.com/en-us/library/dn607317(v=office.15).aspx]

      Demo

      This demo illustrates the configuration of OneDrive for Business redirection in SharePoint Server 2013 Service Pack 1 in environment configured with Directory Synchronization with Password Sync.

      [View:~/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-65/1738.OneDrive-For-Business-Redirection-in-Service-Pack-1.mp4:0:0]

      Standard