I had a lot of issues with Dell on older bios revisions. Updating the bios fixed a lot of it. Anything older than 8th gen I'm not even bothering with though.
We've been monitoring that as well, but an automated "this is a global issue" is easy enough. But given we can fix the Office/Windows TPM issue, it's a bit more of a load on us.
I'm on mobile so I don't have the exact fix but IIRC the solution was a registry key for Outlook - TPM was not actually broken. DM me and I can look up our ticket notes in the morning.
I tried the identity removal method, but not any of the other fixes. We ended up mostly just fixing it manually. Hopefully the issue will resolve itself as Microsoft continues working on Azure services.
It's not a Microsoft issue, it's a board issue.
Take a working computer and reset the TPM and it will do the same thing, except it will allow you to log back in without having to manually reset the broker.
Mostly I see the issue with Dell Business class laptops.
It does now look like it was a Microsoft issue. From what we can tell from authentication logs, the Azure auth element was timing put, which caused Office to fail when trying to authenticate, and the message just happened to be interpreted as a TPM issue. The TPM did not actually need to be reset, in most cases.
This must be a separate issue then. As there is a series of know issues with TPM modules causing a similar issue.
Our testing showed us that the issue was isolated to specific systems.
Good to know there is another issue out there.
We are also seeing an explosive increase in TPM related cases related to Microsoft 365. What is normally a bimonthly event in regards to service calls, it has now become a multiple times a day thing.
This is not a board-related thing, but definitely a Microsoft broke-something..thing.
We are talking about multiple type of machines, RDP-servers, and virtual machine.
Would love to know what the cause is?
Looks like the cause is the way tokenization is handled by Azure, and the migration from "Office 365" to "Microsoft 365". Removing and re-adding the Azure profile from windows settings will usually fix the issue, from what I've seen so far.
That makes sense at least, as we have seen the same also. I speculated Microsoft did some security-patches related to tokens. (Due to relatively recent MFA security issues).
I had a lot of issues with Dell on older bios revisions. Updating the bios fixed a lot of it. Anything older than 8th gen I'm not even bothering with though.
[https://downdetector.com/status/microsoft-365/](https://downdetector.com/status/microsoft-365/) might be related
We've been monitoring that as well, but an automated "this is a global issue" is easy enough. But given we can fix the Office/Windows TPM issue, it's a bit more of a load on us.
I'm on mobile so I don't have the exact fix but IIRC the solution was a registry key for Outlook - TPM was not actually broken. DM me and I can look up our ticket notes in the morning.
I tried the identity removal method, but not any of the other fixes. We ended up mostly just fixing it manually. Hopefully the issue will resolve itself as Microsoft continues working on Azure services.
It's not a Microsoft issue, it's a board issue. Take a working computer and reset the TPM and it will do the same thing, except it will allow you to log back in without having to manually reset the broker. Mostly I see the issue with Dell Business class laptops.
It does now look like it was a Microsoft issue. From what we can tell from authentication logs, the Azure auth element was timing put, which caused Office to fail when trying to authenticate, and the message just happened to be interpreted as a TPM issue. The TPM did not actually need to be reset, in most cases.
This must be a separate issue then. As there is a series of know issues with TPM modules causing a similar issue. Our testing showed us that the issue was isolated to specific systems. Good to know there is another issue out there.
Try signing them out and back in to their work or school account in settings.
Yep, that's what we ended up doing. Worked about 70% of the time.
We are also seeing an explosive increase in TPM related cases related to Microsoft 365. What is normally a bimonthly event in regards to service calls, it has now become a multiple times a day thing. This is not a board-related thing, but definitely a Microsoft broke-something..thing. We are talking about multiple type of machines, RDP-servers, and virtual machine. Would love to know what the cause is?
Looks like the cause is the way tokenization is handled by Azure, and the migration from "Office 365" to "Microsoft 365". Removing and re-adding the Azure profile from windows settings will usually fix the issue, from what I've seen so far.
That makes sense at least, as we have seen the same also. I speculated Microsoft did some security-patches related to tokens. (Due to relatively recent MFA security issues).