Mx records being: and the IP is our firewall Internal domain FQDN is but we don't own that website so we have to use don't ask my why it was setup like that, it was setup like that over 15 years ago lol, for instance: I may be conflating issues here but one thing that I wanted to mention was that our internal domain isn't the same as our actual domain. Thanks, I will try to focus my search there first then.
I really appreciate any insight on where to start to look or what may be the root cause of the issue. I'm not very experienced when it comes to Exchange, we had a 3rd party vendor set this up and manage it for the past 10 years or so and they are no longer going to be with us so I am trying to see if I can find a solution on my own first before looking into other options. maybe it's thinking that we are on O365 and is wanting us to login, but we are not on O365 yet, we just signed up for Teams online. maybe it's something to do with Autodiscover.xml and perhaps something to do with DNS I believe it has something to do with either of these: This is usually what it says when an account is locked out in Active Directory and it wants the AD password. When the pop up occurs, it's asking for you to sign in to Microsoft and it says "Needs password" down at the bottom right of Outlook. This seems to only happen when we add a mailbox (either for the first time or re-add), but we are having issues where it's disconnecting the mailbox completely and the only solution is to remove the mailbox completely and re-add it.
I say that something broke because we now have Microsoft wanting an actual login and popping up quite often on new installs. When we did it, we did sign up for the Teams Exploratory license that was free I think, but not sure if that has anything to do with the issue or not. I think we were going to have to do this process anyways at some point for the O365 conversion next year but maybe I should have just waited until then.Įither way, we did it and I'm fairly certain something in the process broke. I was asked to begin setting up some of our users on Microsoft Teams so we went ahead and set our Organization up on Microsoft and verified our domain/Organization by placing the snippet of code on our website to prove we owned the domain. We use Microsoft Exchange 2016 on prem, we will eventually be switching to O365 next year at some point. Apologies for my ignorance on some of this topic.
0 kommentar(er)
