Office 365 Email Gone After Forced Logoff
-
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
They would also use the concierge program to hand out bad support info. Then blame customers for using bad contact info. AFAIK the entire setup existed just as a way to avoid providing support.
Who would do that? Oh, wait
We escalated through Chris, too, and he could do nothing to get us to working support back then.
-
@tim_g 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:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
If I create a new AD user, it gets synced to O365, but is unlicensed until I go in and manually assign an E1 or E3 license.
It's like that by default, and I want to keep it that way... so I don't know if there's a way to assign those licenses on-prem or not. I don't want anything automatically assigned.
https://gallery.technet.microsoft.com/office/Assign-Office-365-Licenses-b7385ebe
Anything can be done if you know what to do.
-
@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.
Or you could have just called me.
Of course, out of bounds, blame Microsoft and not the guy you gave permissions to the local equipment.
-
@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.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
Of course, out of bounds, blame Microsoft and not the guy you gave permissions to the local equipment.
Well, it sure wasn't me. But I'm definitely the guy that made it crystal clear what they had no permission whatsoever to do.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
All issues this year are 100% licensing, and in no way associated with any past problems.
Not true as the AD sync was discovered earlier this year.
-
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
All issues this year are 100% licensing, and in no way associated with any past problems.
Not true as the AD sync was discovered earlier this year.
Oh that's right, sorry. Yes, a new issue with it popped up. I forgot how recent that was. It had been hidden from me.
-
@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.
