Solved

Office 365 (Enterprise E1) Outlook/DNS Setup

Posted on 2014-01-01
5
1,005 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 11

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

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes w…
During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

623 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