Posts made by PSX_Defector

@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:

Why does this have to be some big, personal thing?

Because you have called into question my integrity, implying shit that is not there.

And it really pisses me off.

Hmmmm... go back and read your posts. You made things up and attacked as your starting point. Why did you do that? Why are you so aggressive about MS making such a simple mistake?

Because you have done this shit in the past, over and over and over and over again.

You know I don't post all the time, and I really could care less about this issue because you have a hate boner for O365. But you constantly do this shit, make unfounded accusations, and they are always some variation of a conspiracy.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

Why does this have to be some big, personal thing?

Because you have called into question my integrity, implying shit that is not there.

And it really pisses me off.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@psx_defector said in Office 365 Email Gone After Forced Logoff:

I've never worked on an account that wasn't bought direct from Microsoft. I don't know where your logs are but they are there.

It's direct from MS. The logs aren't available to us. Does MS have secret logs? Very possibly. But I don't have access to them I don't think.

Then you don't have the correct permissions. That's all there is to it.

@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:

Did you miss the line where I work with AAD on my personal shit? Perhaps I know more than you about O365, AAD, and Microsoft in general?

Working with it on your own stuff would not provide the kinds of information you were claiming. You would know things like "some issues and changes are logged here", but you could not know "that changes could not be made without logging."

Dude, are you stupid? EVERYTHING GETS LOGGED, it doesn't require a rocket scientist to know this shit.

So... you are then claiming that the logs were deleted? Whose the conspiracy theorist?

It's because your account is a vendor reseller most likely. I've never worked on an account that wasn't bought direct from Microsoft. I don't know where your logs are but they are there.

Hence why I was able to login to my personal account, open my AAD grouping, create the account, add the service, and show you the entry.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@psx_defector said in Office 365 Email Gone After Forced Logoff:

Did you miss the line where I work with AAD on my personal shit? Perhaps I know more than you about O365, AAD, and Microsoft in general?

Working with it on your own stuff would not provide the kinds of information you were claiming. You would know things like "some issues and changes are logged here", but you could not know "that changes could not be made without logging."

Dude, are you stupid? EVERYTHING GETS LOGGED, it doesn't require a rocket scientist to know this shit.

Again, basic info from O365 training. And knowledge of how it works. Plus I've had people claim this shit, hence I know where to go.

You are projecting and trying to gaslight me on shit you think you know. Knock it off.

Again, you seem to think I have magic internal knowledge.

Did you miss the line where I work with AAD on my personal shit? Perhaps I know more than you about O365, AAD, and Microsoft in general?

https://support.office.com/en-us/article/Understanding-Office-365-identity-and-Azure-Active-Directory-06a189e7-5ec6-4af2-94bf-a22ea225a7a9

Your external documentation on the O365 and AAD integration. This is also given out in the O365 certification training, which I also possess.

Try again.

OK, let's put this shit to rest.

I NEVER said who I work for, be it whomever I work for now, my previous employers, etc. etc. etc. I know I let it loose a few times, but that was well after I left their employ, e.g. Big Red V. I never have or will use my internal knowledge of places to my advantage in public forums, because I know lots of people and have lots of internal knowledge of various processes and procedures.

My knowledge of the Microsoft ecosystem is my own, because I'm damn good at working with it and have lots of information. My personal lab is setup in Azure. I extend my personal environment with O365 vertical services including AAD. I use Sharepoint Online for development and learning purposes. So I don't have to work for anyone to know everything I need to know.

For all anyone knows, I might work for myself, or work for a vendor, or work for the government. But you will NEVER get an official "I work at blah". So you might have some IRL knowledge, but when I write as PSX_Defector, I speak only for myself. Never question my integrity or imply any official capacity again.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@psx_defector said in Office 365 Email Gone After Forced Logoff:

There will still be USP entries. Because AAD will still need to get something from the billing portal, portal.office.com, so something had to have been applied.

Again, what do you see in AAD? Because as my previous screenshot shows, it says who did what and exactly the stuff done. There will always be an entry,...

So this assessment must not be true. There are no entries. So whether MS makes changes that aren't reflected tehre, or lets us make chances that are not reflected there, nothing was reflected there. So the underlying premise that AAD will always tell us what has happened and that we can troubleshoot this ourselves is fundamentally incorrect. There was no data visible to us. Perhaps MS logs data that is visible only to you, I do not know.

Thinking about this on the drive home, since you have a partner account, it might be in another area.

Instead of going round and round with your non-stop conspiracy shit, I'm giving up. Given you didn't even know about AAD, I'm going with you don't know what you are doing. You don't have the right info in front of you and I'm not about to do your job.

You keep thinking MS is out to get ya.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

Logs are empty for two days before the issue. So whatever MS did, was not logged in a way visible to us.

I posted on here at 9:20am, 12 minutes before the first log entry in AAD.

Microsoft targeted you for funsies, left no trace in AAD, and you are without Outlook?

Oh oh, it's magic!

So someone ganked the O365 partner account, which propagated to the ntg.co domain? That was the issue?

There will still be USP entries. Because AAD will still need to get something from the billing portal, portal.office.com, so something had to have been applied.

Again, what do you see in AAD? Because as my previous screenshot shows, it says who did what and exactly the stuff done. There will always be an entry, because something had to tell your domain that it no longer has Exchange. That feeds back into the portal.office.com site, removing the Outlook link. You can't nuke your service without it.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@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.

How so? Did you find something that did an UpdateServicePrincipal that wasn't executed by you?

Again, your problem statement is "Exchange mailbox popped off user". If you have no USP updates, then that would be on the MS side. If you have USP entries, what do they say?

@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.

@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.

@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.

@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.

https://aad.portal.azure.com

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:

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.

@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.

@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:

@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.

@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.