Forum Discussion
New-ApplicationAccessPolicy
- Aug 09, 2023
The command to check is:
(Get-ManagementRole -Cmdlet New-ApplicationAccessPolicy).Name | ForEach-Object { Get-ManagementRoleAssignment -Role $_ -Delegating:$false | Format-Table -AutoSize Role, RoleAssigneeType, RoleAssigneeName; }
The output of which is:
So, to answer your question: to be able to run New-ApplicationAccessPolicy in a default environment, the account you're signing in with needs to be a member of Exchange's "Organization Management" role.
Cheers,
Lain
It still exists. If you're not seeing it then I'd wager it's because the account your authenticating with does not have access to it.
Have a read of this other thread that is effectively the same question about a different commandlet and see how you go:
Cheers,
Lain
LainRobertson thanks for the quick response, as you suggested I ran the following commands. Now how would I know which role I require to execute the New-ApplicationAccessPolicy cmdlet. Sorry I'm new to powershell and thankyou very much for the help.
- LainRobertsonAug 09, 2023Silver Contributor
The command to check is:
(Get-ManagementRole -Cmdlet New-ApplicationAccessPolicy).Name | ForEach-Object { Get-ManagementRoleAssignment -Role $_ -Delegating:$false | Format-Table -AutoSize Role, RoleAssigneeType, RoleAssigneeName; }
The output of which is:
So, to answer your question: to be able to run New-ApplicationAccessPolicy in a default environment, the account you're signing in with needs to be a member of Exchange's "Organization Management" role.
Cheers,
Lain
- aruncherian95Aug 09, 2023Copper Contributor
LainRobertson Awesome thanks a lot. Really Appreciate your assistance.