I searched so many times about this this problem, but I couldn't find anything. Please help me if you know. I have a B2C on azure portal. In here, there is a policy. If I use this policy to verify the e-mail, it works without problem. But I want to use 2 different policy to send different verification e-mail. So I added new custom policy. But when I click to "run now" sigin_and_signup policy it verified with other verification e-mail. By the way I created APIKey and tenantID(d-abcsdsvxxxxxxx) on the sendGrid portal.
0
votes
Hi, I've added an initial answer based on what you've described here, but if you can add some examples from the current policies you have that would help track down the specific problem.
– Dave D
I can explain step by step. 1. I created custom policy 5 xml page(signin_signup, password_reset,profiledit,TrustFrameworkbase,TrustFrameworkextension).xml 2. edited the tenantID(d-xxxxxx...) in TrustFrameworkbase , edited proxyIdentityExpreinceFrameworkapplcationID and IdentityExpreinceFrameworkapplcationID I click to run now on custom policy(signin_signup). I enter my e-mail address to sign up, it verified with my azure active director(default template).
– yalçın
Hi, @yalçın Please let us know if you are still looking for any Help?
– Raghavendra beldona
1 Answers
0
votes
The docs should be able to help you out with how SendGrid can be integrated with B2C to send custom verification emails. If you want to send a completely customised verification email (instead of the AAD default email) then you need to follow that documentation step-by-step.
If you've already implemented custom email verification templates and your two policies are both using the same template instead of different ones then the part you're probably having problems with is the claims transformation. If you take a look at that section of the docs you'll see that there's a template_id, that's the id of the specific SendGrid email template that B2C will use.
If you want there to be two different custom email templates used then you'll need two different claims transformations, each with the template_id of the email it should be using. You'd also need two SendOtp technical profiles, each using a different claims transformation.
