Solved

Office 365 (Enterprise E1) Outlook/DNS Setup

Posted on 2014-01-01
5
925 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

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Find out what the Office 365 disclaimer function is, why you would use it and its limited ability to create Office 365 signatures.
In a previous video Micro Tutorial here at Experts Exchange (http://www.experts-exchange.com/videos/1358/How-to-get-a-free-trial-of-Office-365-with-the-Office-2016-desktop-applications.html), I explained how to get a free, one-month trial of Office …
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …

919 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

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now