Getting Started with Office 365

Chris Goosen, MVPwww.cgoosen.com

@chrisgoosen

AgendaIntroduction

What is Office 365?

Office 365 plans

Getting started with Office 365

Identity Management

Directory Synchronization

Notes from the field

Useful Resources

What is Office 365?Productivity Applications

Microsoft Office Project & Visio Office Mobile Office Online

Productivity Services

Exchange Online Lync Online SharePoint Online Yammer

Shared Services

• Provisioning

• Identity Management

• System Monitoring

• Licensing

Office 365 PlansOffice 365 licenses are grouped into plans

Business, Enterprise, Education, Government and Nonprofit

plans

Same features, different eligibility criteria and pricing

Business plans have a 300 user limit

Kiosk plans are available for deskless workers

Individual service plans are also available

Different plan families are allowed on the same tenant

Office 365 Plan ComparisonBusiness Essentials Business Business Premium E1 ProPlus E3

User Maximum 300 300 300 Unlimited Unlimited Unlimited

Full, installed Office applications

Office for tablets

Office for smartphones

Office Online

File storage and sharing

Business-class email

Unlimited online meetings

Intranet site for your teams

Social networking

Personalized search and discovery

Enterprise App management

Self-service Business Intelligence

Compliance Information Protection

eDiscovery Center

Getting started with Office 3651 • Sign up for a trial tenant at

deploy.office.com

2 • Add and verify custom domains

3 • Configure DNS

4 • Provision user accounts (Manually/DirSync)

5 • Assign licenses

Getting started with a tenant Sign up for a trial at deploy.office.com

E3 trial recommended

Consider your tenant name carefully

DemoAdd and verify custom domains

DNS configuration

Identity ManagementAzure Active Directory:– The shared identity platform behind Office 365– Integrates with enterprise identity platforms– Enables single sign-on

– Should *not* be confused with running your AD

Domain Controllers as VMs in AzureThree identity management models:– Cloud Identities– Synchronized Identities– Federated Identities

Cloud IdentitiesNo additional hardware

Great if you are “cloud only”

Multiple credentials

Azure Active Directory

AuthenticationManual Creation

.CSV Import

UserAuthorization

Synchronized IdentitiesUp to 2 additional servers

Syncs a hash of password hash

Same sign-on

Azure Active Directory

AuthenticationOn-premises

Active Directory

UserAuthorization

DirSync

Federated IdentitiesMinimum of 3 additional servers

Authentication occurs on-premises

Single sign-on

Azure Active Directory

Authentication

On-premises Active Directory

UserAuthorization

DirSync

On-premisesAD FS One-way trust

Which identity management model??Cloud identities work great if you don’t have an on-premises AD, for testing or simple pilots

Synchronized identities enable same sign-on without the need for federation

Consider synchronized identities unless you specifically require federation

Federation enables true single sign-on and can be leveraged for other SaaS applications

It is possible to change models – keep it simple!

Directory Synchronization (DirSync)Used to sync user, group and contact objects from on-premises AD to Azure AD (Office 365)

Allows these objects to be administered using existing on-premises processes

Users are logon enabled, but not automatically licensed to use services

Ability to sync only a subset of your users through OU, domain-based or user attribute filtering

DirSync vs AAD Sync?Azure Active Directory Synchronization Services (AAD Sync) is a new sync service

Enables sync'ing multi-forest AD environments without the complexity of FIM

Allows advanced provisioning, mapping and filtering rules for objects and attributes

Enables multiple on-premises Exchange organizations to map to a single tenant

DirSync RequirementsWindows Server 2008 with SP1 or later

It must be joined to the on-premises AD

.NET Framework 3.5 SP1 and 4.5.1Objects in AD CPU Memory Hard disk size

Fewer than 10,000 1.6 GHz 4 GB 70 GB

10,000–50,000 1.6 GHz 4 GB 70 GB

50,000–100,000 1.6 GHz 16 GB 100 GB

100,000–300,000 1.6 GHz 32 GB 300 GB

300,000–600,000 1.6 GHz 32 GB 450 GB

More than 600,000 1.6 GHz 32 GB 500 GB

DirSync ConsiderationsThe UserPrincipalName attribute (UPN) must be known to the user and publicly routable

Sync’d attributes cannot be blank, have spaces or invalid characters

SQL server required if on-premises AD has more than 50,000 objects

Need to contact support if sync’ing more than 50,000 objects

Usually easier to set the UPN to match email address

DemoDirSync configuration

Synchronization and attribute flow

Notes from the fieldWorkstation readiness is often overlooked and could cause large project delays

Most AD environments will require some remediation – IDFix can help!

Using an internet proxy? Bypass the proxy for Office 365 URLs

Consider license assignment and management

Useful Resources• Office 365 Deployment Center -

https://deploy.office.com/• IdFix DirSync Error Remediation Tool - http://

www.microsoft.com/en-au/download/details.aspx?id=36832

• The Garage Series for Office 365 - http://channel9.msdn.com/Shows/The-Garage-Series-for-Office-365

Thank-you for attendingQuestions?