An Azure service that provides a hybrid, multi-cloud management platform for APIs.
hi Cameron Horton & thx for sharing urs issue here at Q&A portal,
from what you've described, this doesn't look like a configuration issue. The important part is that APIM reports the notification as Sent, the sender address is the default @mail.windowsazure.com, there were no template or notification changes, and you've reproduced it with both Microsoft 365 and external recipients. If multiple tenants are seeing the same behavior at the same time, that points toward a platform issue rather than a problem with your APIM instance.
I'm not aware of a public advisory or ETA for this. A Microsoft external stuff aka support would need to confirm whether this is linked to the previously reported thread or another ongoing incident. For now, I'd recommend opening a support request and including your APIM instance name, region, timestamps, recipient domains, and message IDs if available. That will let the product team trace whether the emails actually left the notification service or were dropped before delivery.
If this is blocking a production onboarding flow, you may need to use a temporary workaround, such as creating users manually or using an alternative invitation process, until Microsoft confirms the status of the notification service.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
and at my blog https://ctrlaltdel.blog/