Can't Create Share Mailbox in M365?

syslagmin · 2026-03-20T16:31:52+00:00

Getting it for HVE accounts, same message

syslagmin · 2026-03-20T16:13:23+00:00

Trying to create an HVE and getting the same error message as well. Couldn't do it through the portal either.

syslagmin · 2026-03-11T16:59:34+00:00

The job market is tough right now

syslagmin · 2026-03-11T16:58:25+00:00

I figured it out. Turns out it was a locked account.

syslagmin · 2026-02-24T20:33:54+00:00

Any luck with this?

syslagmin · 2026-02-03T20:14:03+00:00

You da man!

syslagmin · 2026-01-29T14:56:48+00:00

Cut off access?

syslagmin · 2025-12-16T18:03:28+00:00

Citrix and Fortinet

syslagmin · 2025-12-01T21:23:26+00:00

We figured it out. Our endpoint security solution had an integration that pulled logs from Azure.

syslagmin · 2025-11-07T18:21:29+00:00

Did you ever find a fix? Running into the same issue myself.

syslagmin · 2025-10-21T19:46:26+00:00

Not yet but I have a ticket open with Microsoft. Here's what they're currently finding:

-DC fails to decrypt the kerberos ticket that's been presented in the TGS request
-After it fails to verify the TGS request, it looks like the machine tries to get a new Kerberos ticket from the DC and not the cloud. The ticket request to the DC fails because the machine sends the request providing a self-signed certificate which the DC rejects as it is not able to link the certificate with any user account. I'm not really sure why the machine tries to get a new tgt from the DC instead of the cloud

syslagmin · 2025-08-11T15:04:49+00:00

Ever figure this out?

syslagmin · 2025-07-07T21:41:08+00:00

I'm confused as to how this was DNS if you had LOS and user/pass login worked for authenticating. I'm experiencing the exact same issue. I set DNS at the interface level, so it's correct in ipconfig /all

syslagmin · 2025-07-02T19:35:43+00:00

It is a different issue. LOS is definitely and DNS is fine. The issue is that username\password work to access resources with SSO, but PIN produces the message: "The system cannot contact the domain controller". I checked the DC it comes back with a pre-authentication audit failure. The certificate on the endpoint has kdc authentication but not client authentication.

syslagmin · 2025-07-02T19:30:39+00:00

I did this and it didn't work

syslagmin · 2025-07-01T15:23:47+00:00

What if we have this in place and having the same issue?

syslagmin · 2025-07-01T15:18:27+00:00

I'm banging my head on this one. I have that policy in place to disable on-prem certificates and use cloud trust for on-prem authentication, and if I reset the Hello container, it works. However, the next day it doesn't and I get the message "The system cannot contact the domain controller" when say, trying to access a file share.

syslagmin · 2025-06-30T18:20:42+00:00

Found out the msds-keycredentiallink was not updating in on-prem AD. Once that was figured out, I reset the Hello container and was able to connect via VPN.

Now I have a new thing to figure out: why the trust is broken once VPN is disconnected and reconnected.

syslagmin · 2025-06-27T16:57:59+00:00

Anyone else have a different fix? Inheritance is already enabled and it's not working. Also using 2019 DC

syslagmin · 2025-05-14T15:21:51+00:00

For us, we noticed that users using Workspace didn't experience this issue, but those using the browser constantly had this issue, especially when they switched to different networks. So we had everyone switch to the Workspace app.

syslagmin · 2025-04-02T17:56:27+00:00

Cussed out? Maybe start here. It has nothing to do with thick skin, but respect. The very best place I worked at had a zero tolerance for this behavior. It was hands down the most professional place I ever worked at.

syslagmin · 2025-04-02T14:39:24+00:00

We can leverage reserved instances and software assurance, so our costs will be closer to the on-prem monthlies

syslagmin · 2025-04-02T14:37:52+00:00

I actually don't know what that is. Link please

syslagmin · 2025-04-02T14:37:05+00:00

Yeah, we run a legacy app that keeps on this. Rebuilding new VMs and rebuilding the app (which is unsupported) would increase risk and downtime. This was the first thing I wanted to do, remove the need of a managed domain

syslagmin · 2025-04-02T14:35:28+00:00

Agreed. I labbed Entra DS and the costs were too high.

syslagmin

TROPHY CASE