Solved

Office 365 (Enterprise E1) Outlook/DNS Setup

Posted on 2014-01-01
5
945 Views
Last Modified: 2014-11-12
I have converted over to Office 365 (Enterprise E1). None of the articles online tell where to point your Outlook or DNS so that clients in the domain can connect to Office 365. The OnRamp process completes successfully but there are no instructions as to what to do next.


Please advise,
Niles
0
Comment
Question by:Niles67
5 Comments
 
LVL 13

Expert Comment

by:Abhilash
ID: 39749776
0
 
LVL 18

Expert Comment

by:Raheman M. Abdul
ID: 39749780
0
 
LVL 11

Expert Comment

by:Technodweeb
ID: 39749838
In the MSOL portal log in as an admin user and on the left side click on Domains. Click the radio button next to the domain you are having issue with and then click the link "View DNS Settings". This will give you all of your necessary DNS settings for your intended purpose statement when you set up your account.
0
 

Accepted Solution

by:
Niles67 earned 0 total points
ID: 39770877
Issue solved.

I made a few points that should help:

 

·         Add a domain suffix ‘domain.net’ in local environment (if internal is .local).

·         Change the suffix for the users.

·         Add a forward lookup zone in dns for ‘domain.net’

 

·         Get a 3rd party cert with the Common name ‘<service name.domain.net>’

and dns as ‘<service name.domain.net’,  ‘enterpriseregistration.domain.net’

 

Note: As discussed below are the common service names used

sts, fs, adfs. They can be anything as per your requirement though.

 

·         We will have to then remove the adfs role and iis role.

·         Then install the adfs role again and run the configuration wizard with the new certificates.

 

·         Try to access the webpage internally.

https://<service name.domain.net/adfs/ls/idpinitiatedsignon.aspx

 

For eg if you have chosen the endpoint as sts

https://sts.domain.net/adfs/ls/idpinitiatedsignon.aspx

 

·         After that comes accessing the same link from external network.

For that you will have to configure the Firewall such that the requests coming from external clients are sent to the ADFS server.


·         Once the firewall and dns is configured then you should be able to access

https://<service name.domain.net/adfs/ls/idpinitiatedsignon.aspx

from the external network.

 

·         Once we are able to access it we should be able to sign on successfully.

 

·         After we make sure that this works, the last step will be federating the domain using the command in Azure Active Directory module for Powershell

Connect-MsolService

Credentials for onmicrosoft.com account

Convert-MsolDomainToFederated -DomainName domain.net.
0
 

Author Closing Comment

by:Niles67
ID: 39781764
I made a few points that should help:

 

·         Add a domain suffix ‘domain.net’ in local environment (if internal is .local).

·         Change the suffix for the users.

·         Add a forward lookup zone in dns for ‘domain.net’

 

·         Get a 3rd party cert with the Common name ‘<service name.domain.net>’

and dns as ‘<service name.domain.net’,  ‘enterpriseregistration.domain.net’

 

Note: As discussed below are the common service names used

sts, fs, adfs. They can be anything as per your requirement though.

 

·         We will have to then remove the adfs role and iis role.

·         Then install the adfs role again and run the configuration wizard with the new certificates.

 

·         Try to access the webpage internally.

https://<service name.domain.net/adfs/ls/idpinitiatedsignon.aspx

 

For eg if you have chosen the endpoint as sts

https://sts.domain.net/adfs/ls/idpinitiatedsignon.aspx

 

·         After that comes accessing the same link from external network.

For that you will have to configure the Firewall such that the requests coming from external clients are sent to the ADFS server.


·         Once the firewall and dns is configured then you should be able to access

https://<service name.domain.net/adfs/ls/idpinitiatedsignon.aspx

from the external network.

 

·         Once we are able to access it we should be able to sign on successfully.

 

·         After we make sure that this works, the last step will be federating the domain using the command in Azure Active Directory module for Powershell

Connect-MsolService

Credentials for onmicrosoft.com account

Convert-MsolDomainToFederated -DomainName domain.net.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Event 4625 - Account Name: _ 3 28
How to remove the name in calendar in Outlook 2016 3 38
Office365 / Outlook 2016 issues 16 25
Server 2016 Configuration 7 18
Finding original email is quite difficult due to their duplicates. From this article, you will come to know why multiple duplicates of same emails appear and how to delete duplicate emails from Outlook securely and instantly while vital emails remai…
Large Outlook files lead to various unwanted errors and corruption issues. Furthermore, large outlook files can also make Outlook take longer to start-up, search, navigate, and shut-down. So, In this article, i will discuss a method to make your Out…
This Experts Exchange lesson shows how to use VBA to loop through rows in Excel.  In order to sort, filter, and use database features, there needs to be a value in each column for every row. When data arrives with values missing, code to copy values…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question