I do not believe this approach will work.
Fundamentally, an Entra account is only authenticated in one tenancy. The one where it was created. When you add it as a guest to another tenancy, that tenancy does not authenticate the guest user itself; it relies on that authentication being forwarded from the tenancy where the user is actually hosted.
The Meraki Dashboard cannot ask the Entra tenant associated with your guest account to authenticate you. Only the source tenant can do that.
A better solution would be to add your Entra to their Meraki Dashboard. To do this is as simple as copying that SHA1 fingerprint from your existing dashboard to their dashboard, like this (this tenant has three SAML authentication sources!).

And then add the SAML roles you use to their system. I tend to do a lot of SAML work in general, so I tend to name my roles:
<Company>-<App>-<Role>
In the example below, IFM is the MSP. This role is intended to authenticate access to the Meraki Dashboard, and this is intended to provide Administrator access. This makes it very clear to anyone looking at the logs which company accessed their system, and who it was.

Also, if you are using Entra, use the "mysigns" style to access the Meraki Dashboard. This is the most powerful way to gain access (and very quick, just two mouse clicks).
