This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 23%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
The ExhangeOnlineManagement module has a command called Get-App.
As seen in the help page for Get-App at https://learn.microsoft.com/en-us/powershell/module/exchange/get-app?view=exchange-ps, there is a parameter called "-Mailbox", but when I run Get-App -Mailbox rickki, I get the error A parameter cannot be found that matches parameter name 'Mailbox'.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
From the help for the Get-App cmdlets' "Description" section:
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet.
https://learn.microsoft.com/en-us/powershell/exchange/find-exchange-cmdlet-permissions
If you need more help you should probably use an appropriate Exchange tag to engage with the right SMEs when you post your question. PowerShell isn't the problem, here.
The system described in that article instructs me to use the Get-ManagementRole cmdlet. But I get the same error with that cmdlet: "Get-ManagementRole is not recognized as the name of a cmdlet ...".
At any rate, I've used Get-App as recently as a few months ago and it worked, so I think I must have the right permissions.
The original problem was "A parameter cannot be found..." That implies that the cmdlet (Get-App) was found (i.e., you had permission to use the cmdlet but lacked permission to use the parameter "-Mailbox".
If the Get-App and Get-ManagementRole cmdlets are both in the same module the Get-ManagementRole cmdlet should be able to be found . . . unless you lack the necessary permission to use the cmdlet (or you aren't connected to O365 or imported the session to get access to the module).
But this still looks like a problem that's not directly related to PowerShell, but to your environment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 43%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBJ%3C/text%3E%3C/svg%3E)
Hi,@Rick Kirkham
Thanks for posting your question in the Microsoft Q&A forum.
According to your description, when you run the Get-App and Get-ManagementRole commands, there is a message that the commands are not recognized.I rather agree with Rich Matheisen that the probability of this happening is still due to the fact that you don't have permission.
Please check that you have the following permissions first, which is a prerequisite for running the Get-ManagementRole command.
See the screenshot below for the permissions needed to run the Get-APP command:
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Just to be clear:
Just to close the loop. These cmdlets work when I use the credentials for my developer tenancy in Microsoft 365. They fail when I use my ordinary corp account. So, it probably is a permissions issue. Thanks for your help.