Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
The way this usually goes - at least my experience many years ago being in development and managing software services, was that there would be some evidence, conflicting, that the issue was localized - specific to a particular computer, group of computers, operating system, etc. And in this case it is - this works on some Mac OSX systems and some it does not.
So the technical people want to know that it's a Microsoft issue affecting Microsoft users and they in a purest sense doesn't want to invest resources to solve a non-Microsoft problem. That would be wrong. So as long as there might be a little chance that it cannot be a MS problem, it gets kicked to the curb.
Meanwhile notice that management just wants to know the process has been followed. If it affects fewer users and can be ignored through a legitimate argument, then ignore it.
Meanwhile nobody noticed that BAD WILL doesn't need numbers. It really doesn't matter if local or not - who is the best group to fix the problem? The ones who designed the product. Sometimes you have to tell the technical folks to just swallow hard and find the real problem and perhaps install a little sub that clears out a cache or link that's allowing the problem even though it was caused by something apple did. That's how outstanding companies think - NOT ON MY SHIFT.