Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Office 365 (Enterprise E1) Outlook/DNS Setup

Posted on 2014-01-01
5
Medium Priority
?
1,055 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 13

Expert Comment

by:Abhilash
ID: 39749776
0
 
LVL 19

Expert Comment

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

Expert Comment

by:Gregory Miller
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

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Microsoft is moving in-place eDiscovery & hold from ECP to EOP console under Content Search in Search and Investigation Options.  In this post, I will be showing you how to export emails to a PST file using the Content Search Options.
The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…

661 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