-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local service principles are removed from groups after migration #546
Comments
@aminmovahed-db What do you mean that "sps don't exist in AD?". Is it even possible? |
Databricks service principals are member of the workspace groups and they
are not member of the corresponding user groups in the databricks account
(since the account user groups are synced from AD and in AD there are only
users). So when the workspace group is deleted and replaced by the account
user group, sp does not belong to any group in the workspace anymore. In
this case, the sp should be manually added to that account user group.
…On Thu, 30 Nov 2023 at 18:56, Serge Smertin ***@***.***> wrote:
@aminmovahed-db <https://github.com/aminmovahed-db> What do you mean that
"sps don't exist in AD?". Is it even possible?
—
Reply to this email directly, view it on GitHub
<#546 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBMKWCK2XLRLWFYXQPKWT7DYHA32FAVCNFSM6AAAAAA63WIN5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI3DSMRXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
As far as I understand, this means that the Service Principal hasn't been added to the account group before doing the group migration. |
If there is a service principle in a workspace group, it will be removed from the account group post migration (since SPs do not exist in AD). Hence, there is a manual step required to identify and add the service principles to the groups after running UCX group migration jobs. It would be great to have such feature to include this manual step into the UCX job.
The text was updated successfully, but these errors were encountered: