Max Melcher

3 minute read

My notes about the session “SharePoint 2013 hybrid end-to-end” by Sam Hassani.

A Hybrid environment combining SharePoint Server 2013 and SharePoint Online can fuse together the very best elements of both systems and offer a seamless experience to end-users when implemented correctly – in addition to providing you with cost savings. Attend this session to understand the solutions SharePoint hybrid environments support. We’ll walk through the end-to-end configuration process covering infrastructure, identity management and SharePoint integration points. We’ll use Search as a real-world example. Hybrid is a real way to begin to take advantage of cloud economics, achieve user-productive scenario benefits and the deployment approach is entirely supported by Microsoft.

Here are my session notes.

Why Hybrid?

O365 + Azure/On-premises = hybrid. This gives you somewhat more flexibility – at higher pace.

IMG_1665{.thickbox}

Hybrid Options

Search: Federated Search is possible for both directions.

Business Connectivity Services (BCS): Add oData sources sitting on-prem.

Duet Enterprise Online: Read & write against on-prem SAP systems

Identity Management: Single sign on and single identity for end users.

IMG_1668{.thickbox}

Enhanced capabilities will be announced for search – single, merged result set would be very nice – I asked Sam after the session if he knows when this will be, probably not at this SPC.

Identity Management

Recommendation is that when you implement DirSync that you take it one step further and implement ADFS for the best user experience – single sign on.

IMG_1667{.thickbox}

DirSync is limited to 50.000 – you can add filters based on OU, Domain or User Attributes – by default every 3 hours.

Azure Ad is a requirement for hybrid scenarios – including search. If you don’t have the current users account in the cloud security trimming wont work and you wont get search results.

You need to add a domain to O365, verify it and then you can activate DirSync.

Configure SSO: Server 2003 R2 and UPN are set if the domain on prem is different. Deploy ADFS 2.0. Install Microsoft Online Services Sin in Assistant and Windows Azure AD PowerShell Modules, setup a trust between ADFS and Windows Azure AD. DirSync is based on FIM.

Sam showed us how to implement a federated search, Query Rules and floating result containers. I knew that already and I skip this for brevity.

IMG_1666{.thickbox}IMG_1671{.thickbox}

Social

Social was another broad topic – where is your User Profile is a key question. Is it on-prem, O365 or even on Yammer. Synchronize them?

IMG_1672{.thickbox}

Summary

That was quite a good session – very thorough information from a to z what challenges you face. Good stuff!

IMG_1678{.thickbox}

comments powered by Disqus