Office 365 Deployment

Patterns and Practices

October 2013

Session Overview

This session details common scenarios for deploying Office 365 services.
Office 365 provides a breadth of capability, but often there is a key
scenario that is the priority. In this session learn about optimal paths for
customers moving from Domino Notes, or customers looking to
incorporate Yammer with Office 365. Future topics will include optimal
paths for: customers with Multiple Forests or multiple tenant requirements,
as well as customers who wish to add additional Office 365 services to
existing Office 365 Pro Plus or stand alone service deployments.
Understand the implications of these deployment approaches and the
steps required to expand the service offerings.

Agenda

Quick Review of the Optimal

paths for Exchange

Optimal Path for Domino Notes

Optimal Path for Yammer

Future Paths

Review Optimal Path

for Exchange

Optimized Path for Exchange 2007

Pilot

Deploy

Cloud ID

PST
Self service

Shared
namespace

Connected
account

PST import
tool

Admin
driven

Syncd ID
and
password

IMAP
migration

Enhance

PST import
tool
IMAP
migration

Admin
driven
Hybrid
servers

Migratio
n
Admin
driven

Change
ID Type

PST

Migration

Change
ID Type

Migratio
n

Admin
Driven

Self service

Hybrid
migration

Migration

Self service
Staged
Migration

Hybrid
migration

Migratio
n
Admin
driven
Federated
ID

Staged
migration

Pilot

Optimized Path for Exchange 2010

Deploy

Cloud ID

PST
Self service

Shared
namespace

Connected
account

PST import
tool

Admin
driven

Syncd ID
and
password

IMAP
migration

Enhance

PST import
tool
IMAP
migration

Migratio
n
Admin
driven

Change
ID Type

PST

Migration

Change
ID Type

Migratio
n

Admin
Driven

Self service

Self service
Hybrid
Migration

Migratio
n
Admin
driven
Federated
ID

Hybrid
migration

Optimal Path for

Domino Notes

1. Pilot Experience
Setup on day 1

Sign-on

Full use of the service

User driven pilot
Pilot setup continues to
step 2 deploy
Limited on-premises
requirements

Pilot the service quickly

User signs into Office 365 with a Cloud ID (jane@contoso.onmicrosoft.com)

Pilot the new Exchange mailbox

Mail

New mailbox in the cloud

Inbox content populated via Connected Account
User sends/receives email as Jane@contoso.com

Pilot the new collaboration tools

Collaboration

Clients

Run online meetings with any user with computer

PC-to-PC calling, video conferencing, and app sharing.
Collaborate using SharePoint Online team site and newsfeeds
Easily store files in the cloud with SkyDrive Pro and share file with external users

Office across multiple devices

Access the service via a browser - Office Web Apps across devices and platforms (no
client required)
User self-install of Office 365 ProPlus side-by-side with existing Office client installations

Experience Office anywhere

Mobile

Mobile connectivity options are built into the service just start connecting devices
Connect to Office 365 via mobile devices with Exchange Active Sync for mail
Platform specific mobile apps bring best experience where it makes sense - i.e.
OneNote, Lync

Control & manage your pilot

Administration

Centralized administration from the Office 365 admin center in the service
Online management centers for Exchange, SharePoint, and Lync
Service health dashboard to monitor service maintenance and incidents
Service use reporting available in the service admin center including service activity

1. Pilot What is required

Simple requirements

Network

Easy to start or stop

Mail
Clients

What you need to connect

Network access to service from client end points over ports 80 and 443
Network bandwidth capacity

Connect to existing mail for the pilot

POP3 or IMAP4 protocol support for pilot users to use Connected Accounts

Pilot user access

Web client minimum browser
Office 365 Pro Plus clients running Windows 7 +

2. Deploy Experience whats added

Setup in days
Adds on-premises
integration
Pilot user and info is
sustained

Sign-on

Sign-on with the same user name as on premises

Integrated mail flow

Mail

Shared SMTP domain and connectors facilitate mail flow between Office 365 and onpremises org
Global address list (imported)
Additional users email content migrated via Connected Accounts

Sharing and working with others

Collaboration

IT driven migration
Mail migration that
best fits environment

Shared namespace

Lync business partner federation

Site governance and provisioning support
Setup of Apps for Office corporate app catalog

Clients

IT managed client productivity

Mobile

Managed mobile connectivity

Administration

Office 365 ProPlus deployed to user desktop via IT process

Send and receive mail from mobile device as on-prem email

Control & monitor

Data loss prevention configuration (limited)
Exchange Online Protection mail protection configuration (limited)

2. Deploy whats required

Dedicated customer IT
team
Change management
readiness

Identity

Whats Required
Populate online directory
Set Identity equal to on-prem user name

What you need to connect

Network

Mail
Clients

Network access to service from client end points

Network bandwidth availability
Access to maintain DNS entries for shared domain(s)

Required to setup and migrate

Admin access, managed by customer IT team

Required to connect and deploy

Web client minimum browser
Office 365 Pro Plus clients running Windows 7 +

3. Enhance- Whats added

Adds scenarios
Extended durations
Customer specific
implementation
Ability to add to
deployed clients at
point in the future

Sign-on
Mail
Management

Advanced integration
Single sign-on / ADFS
3rd party identity providers Works with program

Advance migration scenarios

Notes mail, calendar, and contacts data migrations

Directory integration
Sync Domino Directory to on-prem AD via 3rd party tools
Sync on-prem AD to MSOnline Directory Services

Advanced integration and solution building

Collaboration

Richer coexistence with on-prem Notes org, incl. Free/Busy information sharing via 3rd
party tools
Lync or SharePoint hybrid
SharePoint solutions including BCS, Duet, etc.

Clients

Advanced client management capabilities

Mobile

Connect to the service

Administration

Virtual desktop and virtual application scenarios

Blackberry Enterprise Sever integration

Leverage advanced service controls

Data loss prevention configuration
Exchange Online Protection mail protection configuration

Optimized Path for Notes

Migrations

Pilot

Deploy

Enhance

Cloud ID

IMAP
Migration
(Email
only)

Admin
Driven

Self service via

connected
accounts

Office
Pro Plus

Admin
Driven

Self service

Shared
namespace

Directory Prep
(Domino & AD)

Sign-on using
customer domain

Directory Sync
(AD to Office
365)

Simple
Coexistence
(mail routing)

Self service

Import Remaining
Users (unified GAL,
no DirSync)

Office
Pro Plus
for
additional
users

IMAP Migration
for additional
users

Admin
Driven

Syncd ID
and
password
Change
ID Type
Federated
ID
(ADFS)

Enhanced Coex
Free/Busy
(3rd party tools)

Enhanced data
migration
(3rd party tools)

Optimized path Domino Notes

Recap

Pilot service in about an hour

Deployment options to meet your requirements
Leverage 3rd Party tools for IT led migration in Step 3

Decision points
Identity type
Namespace
Coexistence
Migration approach
Authentication requirements

Optimal Path for

Yammer

1. Pilot Experience
Enroll on day 1

Sign-on

User-driven pilot
Create internal and
external networks
Limited on-premises
requirements

Pilot the service quickly

EnrollO365 tenant for afree Yammer Basic network with a Cloud ID (
jane@contoso.com)

Pilot the Yammer collaboration tools

Collaboration

Replace the SharePoint Online Newsfeed in the Office 365 header with Yammer
OR
Incorporate Yammer web parts into Team and My Sites in SharePoint Online

Clients

Yammer across multiple devices

Mobile

Experience Yammer anywhere

Administration

Web browser, Yammer desktop app

Mobile clients for Windows Phone, Android, Blackberry, iPad, iPhone

Self -service
Users navigate to sign-up URL and enter an email address to join

1. Pilot What is required

Simple requirements

Network

Single Namespace

What you need to connect

Network access to service from client end points over ports 80 and 443
Firewall/Proxy/Filtering/E-mail Whitelists

Browser requirements

Browser

Internet Explorer 8 or later

Firefox (latest version)
Chrome (latest version)
Safari (latest version)
Java-script enabled
Flash 9 or higher

Requirements

Clients

Windows Phone 7 and higher

Android v2.2 and higher
iOS v5.0 and higher
Windows XP and higher
Mac OS 10.5 and higher
Adobe Air (desktop only)

2. Deploy Experience whats added

Setup in days

Control & monitor Yammer Enterprise enrollment

Yammer Enterprise
Customer Success
Manager
Administrative Control
Pilot users and info are
sustained
Provisioning tools for
creating users

Administration

Yammer Enterprise Admin Tools

Network Level Apps & Integrations
Support & Services
Content Sharing (P1 & E1)
Team Sites, notebooks and mailboxes (P1 & E1)
Search (P1 & E1)
SharePoint Store (P1 & E1)
Content Management (P1 & E1)
Office Web Apps (E2)
Hosted E-mail (E2)
Simple File Sharing (E2)

2. Deploy whats required

Dedicated customer IT
team

Identity

Change management
readiness

Network

Whats Required

Clients

Must designate a Verified Admin when working with Yammer Customer Support
Manager to upgrade to Enterprise
Create users in bulk using a CSV
Create users in bulk by implementing Yammer Dsync for directory synchronization

What you need to connect

Network access to service from client end points

Required to connect and deploy

Network access to service from client end points

3. Enhance- Whats added

Adds scenarios
Extended durations
Customer specific
implementation

Custom integration

Integration

Single Sign-On
SharePoint 2010 integration
Yammer Embed
Yammer for Salesforce
Data Export & API

Optimized Path for Yammer

Pilot

Basic
Network

Deploy

Enhance

Cloud ID

Integration
with
SharePoint
Online

Convert
to Paid
Network

SharePoint
Newsfeed
replacement
Syncd ID
Yammer
Web Parts

Change
ID Type

Federated ID

Optimized path for Yammer

Recap

Pilot free service in about an hour

Deployment options to meet your requirements
Leverage bulk provisioning or Synchronized IDs after
conversion to paid service
Optionally enhance service over time for Federated login
Decision points
Identity type
Single Namespace
Convert to Paid
Authentication requirements

Future Paths

Paths we are working on

Multi Forests with single tenant*

Single Forest with multiple tenants
Multiple Forests with multiple tenants
Yammer with multiple namespaces
Single network with multiple namespaces
Multiple networks

Adding services
Start with O365 Pro Plus and add O365 Suite
Start with O365 Pro Plus and add O365 Stand alone services (EXO, SPO, LYO)
Start with SPO and add O365 Suite
Start with SPO and add other stand alone services (O365 Pro Plus, EXO, LYO)
Note: Scenarios in Red next optimal paths to be added. (* This scenario will be Multiple Accounts Forest w/Exchange in
Resource Forest model moving to Single Office 365 Tenant)

24