User Profile
tantonyrei
Copper Contributor
Joined 3 years ago
User Widgets
Recent Discussions
Re: Azure AD connect with existing O365 user accounts
Thanks, because its when I added my company.com domain to the existing company.onmicrosoft.com, the user's Outlook and O365 logins stopped working. That's where I'm stuck now. I choose skip this and do this later because I wasn't sure what option to select, may be that's why.12KViews0likes0CommentsRe: Azure AD connect with existing O365 user accounts
Hi FcoManigrasso, thanks for the reply. Correct, I understand TXT record is only for the initial domain verification and once the domain is verified, we can remove the TXT record from DNS. Yes, I saw the screen after adding domain to modify the MX, CNAME etc, but I wasn't sure what to select there, so I selected 'skip this option', could that be what caused the whole issue? Sorry I'm new to O365, so I don't understand what does that have to do with user's Outlook prompting for passwords. Our exchange server is on premise 2013.12KViews0likes8CommentsRe: Azure AD connect with existing O365 user accounts
Sorry for the late reply. My local AD is a .local, so I added company.com UPN to my AD. My O365 is company.onmicrosoft.com, so I added company.com to the domain, but as soon as I added it, the user's Outlook stopped working and it kept asking for their password, even though I had company.onmicrosoft.com as the default. But when I removed the company.com domain from O365 admin center, the user's emails returned back to normal and working. I'm not sure what caused it. When I added company.com to O365 originally, it asked me to add some TXT records to my DNS and I did. It kept saying that my company.com domain was already associated with another O365 account, which my collogue created for testing, so I removed company.com from the O365 account my collogue created so I could add it to the 'live' O365 account.12KViews0likes10CommentsAzure AD connect with existing O365 user accounts
My overall plan is to migrate our Exchange 2013 server to Exchange Online. If I'm right, it will be easier if I install Azure AD Connect on our AD so it will sync with O365 and users can sign in with their AD account instead of their onmicrosoft.com account. My domain is a .local domain so I'm getting 'TopLevelDomain' error when I run IdFix tool, so I added a new UPN in .com format so I'm not getting that error anymore. What would happen when I sync Azure AD with the user accounts if some of them are already in O365? Does it create duplicate accounts for these users? Also, do I verify my .com domain in O365 before or after syncing with Azure AD?14KViews0likes14Comments
Recent Blog Articles
No content to show