hybrid dilemma: dividing content between azure, office 365 & sharepoint 2016
TRANSCRIPT
Adam levithanDirector Product Management, Metalogix
@collabadam
Hybrid Dilemma: Dividing Content Between Cloud, Office 365 & SharePoint 2016
What’s the Scenario
• Access to documents and content - regardless of technical issues
• Ownership of information
• Ease of Use
• We already purchased it
Business Needs
What’s the Scenario
• Keeping all users engaged and active (no matter where they are or
how they connect)
• Providing the best possible speed and access to content even
through disruptions
• Keep confidential information shared with partners/agencies in
approved environments (and safe)
• Keep information authoritative across all systems
Business Concerns
Challenges
Authentication, Authorization & Permissions
You
Microsoft
Azure AD
3rd party clouds/hosting
Challenges
Service Level Agreements (SLA)
Controlling Roll-out of Features
Regulations/ Compliance
Security
Case Study: Moving Workloads
Identity/ Authentication
Reco
rdTem
po
rary
Typ
e o
f C
onte
nt
Instant Message
Social
Team Sites/ ExtranetEFSS
Intranet
Document/
Records Management
Individual Team Enterprise
AudienceOriginally presented at Portal Solutions http://www.portalsolutions.net
Case Study: Distribution of Content
On-Premises On-Premises
Identity/
Authentication
Hybrid
Customized Business Process
Document/ Records Management
Team Sites
Intranet
Regulated E-mail & Archives
Cloud
EFSS
Extranet
Social
SharePoint 2016 Hybrid
Hybrid Picker
OneDrive for Business
Profile Redirection
Office Graph/ Delve
Team Site Follow
Mobile
Hybrid App Launcher
Data Loss Prevention
Hybrid Search
Content Cleanup16
3 Approaches
rule-based cleansing
business users/content owners for subjective
analysis
Combination of both
ROT Analysis
Redundant
Outdated
Trivial
ROT Options
Migrate
Migrate and Update
Archive
Delete
• Authentication / SSO / ADFS / Azure
AD
• Network topology, Latency &
Throttling of Transactions
• Look & Feel/ User experience
differences
• Keeping information up to date -
Authoritative information
• Compliance / Risk
− PII regulations
• Availability of APIs / limitations of
what content can be accessed
• Backup Services
C
Considerations