Presentation is loading. Please wait.

Presentation is loading. Please wait.

DNS DNS changes required to validate domains in Office 365 UPN – User Principal Name Every user must have a UPN UPN suffixes must match a validated.

Similar presentations


Presentation on theme: "DNS DNS changes required to validate domains in Office 365 UPN – User Principal Name Every user must have a UPN UPN suffixes must match a validated."— Presentation transcript:

1

2

3

4

5

6 DNS DNS changes required to validate domains in Office 365 UPN – User Principal Name Every user must have a UPN UPN suffixes must match a validated domain in Office 365 Users need to use UPN to log in to Office 365 Active Directory Cleanup Data cleansing: Data quality, missing attributes

7 StructureDescriptionConsiderations Matching domainsInternal domain and external domain are the same e.g. contoso.com No special requirements Sub-domainInternal domain is a sub-domain of the external domain e.g. corp.contoso.com Requires domains to be registered in order, primary and then sub-domains Local domain or single label domain Internal domain is not publicly “registered” e.g. contoso.local Domain ownership can’t be proved, must use a different domain: Requires all users to get new UPN Use SMTP address if possible Multiple distinct UPN suffixes in single forest Mix of users having login UPNs under different domains e.g. contoso.com and fabrikam.com ADFS QFE—to resolve this issue. Requires new switch in Windows PowerShell SupportMultipleDomain Multi-forestMultiple AD forestsContact Microsoft

8

9 Set Up ADFS Servers Set Up ADFS Proxies Implement Load Balancing Register DNS

10 Microsoft Online AccountsFederated IdentityExternal Sharing

11 Contoso Customer Premises 1. Microsoft Online IDs AD Microsoft Online Directory Sync Identity Platform Provisioning Platform Lync Online SharePoint Online Exchange Online Federation Gateway AD FS 2.0 Trust IdP Directory Store Admin Portal Authentication Platform IdP Office 365 Desktop Setup Microsoft Online Services 2. Microsoft Online IDs and DirSync 3. Federated IDs and DirSync

12

13

14 1. Microsoft Online IDs Appropriate for Smaller orgs without AD on-premises Pros No servers required on-premises Cons No SSO No two-factor authentication Two sets of credentials to manage with differing password policies IDs mastered in the cloud 2. Microsoft Online IDs and DirSync Appropriate for Medium/large orgs with AD on-premises Pros Users and groups mastered on-premises It enables coexistence scenarios Cons No SSO No two-factor authentication Two sets of credentials to manage with differing password policies Single server deployment 3. Federated IDs and DirSync Appropriate for Larger enterprise orgs with AD on-premises Pros SSO with corporate credentials IDs mastered on- premises Password policy controlled on-premises Two-factor authentication possible It enables coexistence scenarios Cons High availability server deployments required

15

16

17

18 Content Assessment Capture relevant metadata: Type of data Size of data Age of data Migration Planning Should I move? Should I move to online services? What should I do with: Web apps Site collections Sites Document libraries

19 Define the selection criteria Assess how much content is left when criteria are applied

20

21

22

23 Content, Web Parts, etc. End-User Customizations Page layouts, master pages, etc. Authored Customizations Compiled code, timer jobs, etc. Developed Customizations

24 ProcessData Out of the Box/Template Custom Tables Forms Lists Integrations Complex workflows Custom code

25

26 Provisioning/License impact. Users Needed for remediation Feature usage

27

28

29 Migration Plan Information Architecture Where Site collections Sites Managed paths Content types Content Cleanup What Exclusion criteria Inclusion criteria Everything in between Migration Tools How Small-midsize content File Explorer SharePoint Workspace Manual upload Large-scale content Staging environment Third-party tools

30 Self-service migration Manually Tools-based migration Manually using tools Complex migration Includes custom code Involve experts

31

32 Commitment Strong steering committee Realistic Timelines Expectation-setting Knowledge DevelopmentKnowledge management People Source system knowledgeTarget system knowledge

33

34

35 Wed 1:45pm – SPC218 - SharePoint Online Hybrid: Configuring BCS and Duet Online Tue 09:00am – SPC243 - Hybrid Overview Wed 3:15pm - SPC150 - Microsoft Early Learning: Moving Search to O365 and Building a Hybrid Experience Thurs 9:00am - SPC140 - Deep dive on Server to Server OAuth Identity Platform Tue 10:30am - SPC125 - Hybrid and Search in the Cloud

36 MySPC

37


Download ppt "DNS DNS changes required to validate domains in Office 365 UPN – User Principal Name Every user must have a UPN UPN suffixes must match a validated."

Similar presentations


Ads by Google