The TargetAddress attribute is set on the mailbox that the end user is NOT working in for the moment. When migrating, you most likely have a tool like Migrator for Notes to Exchange from Dell Software (formerly know as NME or Notes Migrator for Exchange from Quest Software) to handle to setting of the TargetAddress attribute. In on-premises Exchange systems you can get your hands on the TargetAddress easily by launching Active Directory Users and Computers, switch to Advanced Features and the find the attribute among all other attributes in the “Attribute Editor” tab. The more common use for this attribute is to hold the external address of a MEU or a contact, but that is not a part of this blog post. In the migration case it’s most likely to be sent to either the source or the target email system, depending on the migration status of the mailbox. If forwarding is set for a mailbox that means that all incoming email bound for that particular mailbox is resent, and routed, to some where else. So, what is the role of the TargetAddress attribute? For email migrations, the short answer is: Forwarding. The role of the TargetAddress attribute in migrations What does that mean? Well, the most basic type of coexistence is when the migrated and not migrated users can send email to each other without any hassles. But this is not my intention as this value should be assigned by an admin and not by the user, my intention is to get it as part of the claims.ġ - How can I edit this value from Azure blades UI (I can only see the Built-In attributes, not the custom ones)?Ģ- Can I do this programmatically (PowerShell, C#, GraphAPI, etc.For those of you that have been on email migration assignments, especially from Lotus Notes and Novell Groupwise, you probably know that the TargetAddress attribute is your best friend for basic coexistence. I added, via Azure blades UI, a Custom Attribute of type String and named it RoleAttr and assigned it against the B2C_1_SignUpSignIn User Flow (Policies) and added it to the Application claims.įor testing purposes, all done via UI, if I add this attribute to User attributes, when a user is signing up, he/she is getting a new field called RoleAttr, which means it is working (I guess?!). Other threads are recommending Custom Attributes to simulate this: Security Groups (Application Roles) are not currently supported in Azure AD B2C and it is the highest requested feature on the Azure AD B2C Feedback:

Attribute edit ad