Forum Discussion
Trouble with impersonation using custom write scopes
Dear all,
in the tenant of a customer we have now configured the Exchange impersonation. In the past I have done this many times with OnPrem servers creating a new write scope based on an OU which never was a problem.
Now in O365 we are not able to base this on an OU so we have chosen the ExchCustomAttribute1 which we filled with a specific string. Unfortunately it does not work at all. We tested it with the application outside of O365 and with the Remote Connectivity Analyzer (EWS section for service account access). Both fails.
Interestingly if I change the writescope to default it works immediately.
Is it possible that there are issues with the custom write scopes in Exchange Online?
Kind regards,
woelki
That's all you should need to configure, excluding the obvious mismatch between the "MyString" value you referenced in as being stamped, and the fact that the actual attribute name is "CustomAttribute1". So I'd say double-check your settings, and make sure the filer you are using for the scope actually matches the given users.
I haven't had issues restricting impersonation via scopes in ExO, what are the exact steps you are following?
Creation of a service account "ExchImpersonation"
Tagging the accounts which should be impersonated with "MyString" in ExchCustomAttribute1
New-ManagementScope -Name "Sales" -RecipientRestrictionFilter {ExchCustomAttribute1 -Like "Sales*" }New-ManagementRoleAssignment -Name "Sales_Impersonation" -Role "ApplicationImpersonation" -User "ExchImpersonation" -CustomConfigWriteScope "Sales"
That's it. May I have forgotten a further option for creating the management scope?
That's all you should need to configure, excluding the obvious mismatch between the "MyString" value you referenced in as being stamped, and the fact that the actual attribute name is "CustomAttribute1". So I'd say double-check your settings, and make sure the filer you are using for the scope actually matches the given users.
