"To create the vault, you need role assignment permissions on the resource group in which the Azure Migrate project resides." what is the permission we need? There are no permissions called "role assignment". Please clarify.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ctahok Thanks for the feedback! We are currently investigating and will update you shortly.
@ctahok AFAIK, those required role assignment permissions are explained under Assign role assignment permissions section in the same referred document.
@rayne-wiselman Please provide your insights or clarification, if any.
Thanks Krishna,
But even there if we are configuring the permissions we do it with the aim
of running assessment, then what is the point of calling out small chunk of
permissions here
https://docs.microsoft.com/en-us/azure/migrate/tutorial-prepare-vmware#assign-permissions-to-create-project
then the one you mentioned here
https://docs.microsoft.com/en-us/azure/migrate/tutorial-prepare-vmware#assign-role-assignment-permissions
where
it mentions "In the resource group in the Azure portal, select Access
control (IAM). " which resource group? Why do we even bother with RG level
permission if for running assessment we need contributor or owner
permission? Then Developer role comes into play. Why do not you just make a
simple table with required permissions?
These permissions are all over and it is hard to comprehend what is the
minimum permissions we need.
Regards, Ilkin
On Sun, Dec 8, 2019 at 4:44 AM KrishnaG-MSFT notifications@github.com
wrote:
@ctahok https://github.com/ctahok AFAIK, those required role assignment
permissions are explained under Assign role assignment permissions
https://docs.microsoft.com/en-us/azure/migrate/tutorial-prepare-vmware#assign-role-assignment-permissions
section in the same referred document.
@rayne-wiselman https://github.com/rayne-wiselman Please provide your
insights or clarification, if any.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/44197?email_source=notifications&email_token=AEC6DESUMYKLOYC2NTSFMJ3QXR3RFA5CNFSM4JWTLNIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGV2HQ#issuecomment-562912542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEC6DEQKPVDYHBJ3UVX2GMLQXR3RFANCNFSM4JWTLNIA
.
@anvar-ms Could you please share your thoughts on the previous post?
I will review the permissions content and consolidate into a single place as needed. thx
Thanks very much Rayne. This would be very helpful for CSPs like us to help
our customers.
Regards, Ilkin
On Mon, Dec 9, 2019 at 6:06 AM Rayne Wiselman notifications@github.com
wrote:
I will review the permissions content and consolidate into a single place
as needed. thx—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/44197?email_source=notifications&email_token=AEC6DET4P342J7WRVJ3FF63QXXOAFA5CNFSM4JWTLNIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGH6M4I#issuecomment-563078769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEC6DEUKNGF3AGLCP4LDJSTQXXOAFANCNFSM4JWTLNIA
.
I've updated this page with a table summarizing Azure permissions. The change should show up later today. Let me know if there's anything else.