Office 365 Email Gone After Forced Logoff
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
MS concierge did it himself. That would be Greg. And yes, it was done locally, without permission. In fact, he was explicitly forbidden to do so.
Then you should have purged out the objects out of AAD, set them back up correctly, and then hit the gym.
It's been fine for a long time. It's just every time we have an issue, someone blames MS having done that years ago. But that's not been a problem for a really long time.
OK, so it's a canard if AD Sync has been removed and you are relying on AAD only. If it's in place, there is plenty of possibility of something local to your AD environment telling it to remove the licenses. See previous script.
Shit doesn't disappear magically. I've got a few mailboxes on my 365 setup, with no AD Sync, and haven't lost any of them. Something specific to the NTG setup is causing a problem. There is tons of information on the backend that will tell whomever has the ticket what the hell happened.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Shit doesn't disappear magically.
When our files disappeared, it was nothing to do with AD Sync. MS just lost the account back end. My guess is they mucked about with stuff and hosed it and refused to admit it.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Something specific to the NTG setup is causing a problem. There is tons of information on the backend that will tell whomever has the ticket what the hell happened.Except it happens outside of NTG, too. We've had customers and personal accounts have it happen. Like my personal, non-NTG, nothing to do with NTG account. And it happened without me involved.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
There is tons of information on the backend that will tell whomever has the ticket what the hell happened.
Yes, I agree, I'm sure the issue is MS hiding it. I'm pretty certain that they aren't THAT clueless. They hosed it and hoped to cover it up.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
There is tons of information on the backend that will tell whomever has the ticket what the hell happened.
Yes, I agree, I'm sure the issue is MS hiding it. I'm pretty certain that they aren't THAT clueless. They hosed it and hoped to cover it up.
Grab the tin foil.
Dude, you should know better than to think there is some kind of conspiracy.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Something specific to the NTG setup is causing a problem. There is tons of information on the backend that will tell whomever has the ticket what the hell happened.Except it happens outside of NTG, too. We've had customers and personal accounts have it happen. Like my personal, non-NTG, nothing to do with NTG account. And it happened without me involved.
Right now, all I am hearing is NTG. I've never seen it, a few of my peeps I work with have never had this happen.
Shit disappearing is less conspiracy and more someone mucking up something. And MS is far too big and far too busy to do it for funsies.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Something specific to the NTG setup is causing a problem. There is tons of information on the backend that will tell whomever has the ticket what the hell happened.Except it happens outside of NTG, too. We've had customers and personal accounts have it happen. Like my personal, non-NTG, nothing to do with NTG account. And it happened without me involved.
Right now, all I am hearing is NTG. I've never seen it, a few of my peeps I work with have never had this happen.
That's always the MS answer... blame the customers. That's how MS keeps getting away with shit products and shit support. No matter how many people have it happen, no matter how many customers in a room all see the same things, MS always tries to customer shame.
It's true, we made one big mistake, doing business with MS. Problem resolved.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Shit disappearing is less conspiracy and more someone mucking up something. And MS is far too big and far too busy to do it for funsies.
Tell that to Chris. He was aware. He looked into it. MS could NOT fix lost data. They just... stop providing support. You are right, they are too big to bother with just small outages or lost data. They just... ignore customers with issues. They don't have time for quality.
-
I always blame the customer, doesn't matter whom I work for. Default is ALWAYS the customer messed up something.
When shit blows up on our end, we know it. When one guy complains about a strange thing, then it's on them to prove otherwise.
This conspiracy shit is exactly that, shit.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
I always blame the customer, doesn't matter whom I work for. Default is ALWAYS the customer messed up something.
When shit blows up on our end, we know it. When one guy complains about a strange thing, then it's on them to prove otherwise.
This conspiracy shit is exactly that, shit.
Calling one company not being very competent is not related to a conspiracy. It's just a big company with loads and loads of low cost offshore support. in fact, it's thinking that all people everywhere in teh world having issues are conspiring against a single company that's a conspiracy.
This is, in fact, the opposite of a conspiracy. Just one sloppy vendor.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
When shit blows up on our end, we know it.
Which makes pretending it doesn't happen much worse. Although we've been in meetings with MS where they've claimed that they didn't know it and were surprised to find out that certain outages were common.
It's nice to claim that by being big and rich that you are infallible. But we both know that hubris like that is exactly what makes companies bad at IT. The more hubris there is, the worse the service is.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
When shit blows up on our end, we know it.
Which makes pretending it doesn't happen much worse. Although we've been in meetings with MS where they've claimed that they didn't know it and were surprised to find out that certain outages were common.
It's nice to claim that by being big and rich that you are infallible. But we both know that hubris like that is exactly what makes companies bad at IT. The more hubris there is, the worse the service is.
Ugh. If you think it magically purged, let's see what the logs say.
Login as an administrator, go to Azure Active Directory, then audit log. It will show everything that happened. Look for UpdateServicePrincipal entries. Should say who did what and when:
-
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
If you understood how things work with it, you would know that AAD is the function of O365's service stuff. AD Sync pulls your users into AAD. Federation makes your AD the authoritative resource.
Pull the log, see what you find.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
If you understood how things work with it, you would know that AAD is the function of O365's service stuff. AD Sync pulls your users into AAD. Federation makes your AD the authoritative resource.
Pull the log, see what you find.
But none of that is what we are having issues with.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
If you understood how things work with it, you would know that AAD is the function of O365's service stuff. AD Sync pulls your users into AAD. Federation makes your AD the authoritative resource.
Pull the log, see what you find.
But none of that is what we are having issues with.
You are saying that all your Exchange accounts have popped off your user accounts.
AAD will tell you what you need to know.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
If you understood how things work with it, you would know that AAD is the function of O365's service stuff. AD Sync pulls your users into AAD. Federation makes your AD the authoritative resource.
Pull the log, see what you find.
But none of that is what we are having issues with.
You are saying that all your Exchange accounts have popped off your user accounts.
AAD will tell you what you need to know.
So you are saying that Azure can tell us the billing and account information that even MS couldn't find for three hours? If MS has these resources, why didn't MS use them to determine what was wrong?
-
Someone needs to train the MS employees. Hours and hours today, and MS couldn't find what was wrong for the longest time. Would be nice if MS staff knew that there were ways to just look this up. It took a long time just to find a department that could work on the issue.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector Yes, but most issues are not related to Azure. We get no logs of account issues.
If you understood how things work with it, you would know that AAD is the function of O365's service stuff. AD Sync pulls your users into AAD. Federation makes your AD the authoritative resource.
Pull the log, see what you find.
But none of that is what we are having issues with.
You are saying that all your Exchange accounts have popped off your user accounts.
AAD will tell you what you need to know.
So you are saying that Azure can tell us the billing and account information that even MS couldn't find for three hours? If MS has these resources, why didn't MS use them to determine what was wrong?
Gotta know how to read between the lines. There is deeper info on the MS side of things obviously, but my guess? You don't have a very high support contract level so its just SevC at the moment.
Azure, by extension O365, unless you pay for support, is self service. Lots of things you need to do for yourself. But on the other side, there is TONS of info you can find on your own. You just need someone to show you how.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Azure, by extension O365, unless you pay for support, is self service. Lots of things you need to do for yourself. But on the other side, there is TONS of info you can find on your own. You just need someone to show you how.
Well, that's only so useful when the end result is "stuff on the MS side." So knowing that for sure from AAD, or not, same thing. Gotta call in and wait for support to get their stuff together. Going into AAD wouldn't have gotten us any further since the issues weren't on our end.
