Does anyone know why AD B2C sms sometimes uses "Microsoft" as sender instead of phone number?
It's very weird, sometimes I get Microsoft as sender ID, sometimes I get a phone number, it's very inconsistent and affects the brand of the app.
How do we change this?
I apologize for the delayed response! I have reached out to the product team to ask why the experience is inconsistent. I am not sure whether this is related to the carrier, configuration, or something in the overall experience that changes what gets displayed.
There have also been multiple pieces of product feedback left to add the ability to customize the sender, and I have created a work item to bubble this up and ask for an update on this feature as well (as having this capability would also resolve the problem).
An update on this from the product team -
This is not specific to B2C, but MFA as a whole. The behavior you are seeing comes down to the carrier. Depending on their configurations, which carrier it is, and more, the caller ID might be shown or not. There isn't a lot of documentation on this, but we have this for on-prem MFA servers that provide an explanation. It's related to calls, but the issue would be the same: Azure AD Multi-Factor Authentication FAQ - Azure Active Directory | Microsoft Docs.
So if the SMS happens to be routed by a carrier that doesn't support the ID, it will show as just the number instead of Microsoft. This would be outside of our control, so there is no way to ensure that it always shows our ID.
That said, I have passed along a feature request to make the SMS sender name customizable for the carriers that support it.
I hope this helps.
Marilee
If this information was helpful to you, please remember to "mark as answer" so that others in the community with similar questions can more easily find a solution.
10 people are following this question.
