Hi Webb, Mike
The Remove-AppxPackage cmdlet only works in the context of the logged-in user session, so if you’re trying to run it remotely or under a different account, it’ll throw those permission errors even if you’re technically an admin. That’s why RDC or Invoke-Command isn’t cutting it. The trick is that Microsoft Store apps are user-scoped, not machine-scoped, so you need to run the removal in the actual user’s context.
What usually works is using Remove-AppxProvisionedPackage for system-wide removal, which strips the app from the image so new users don’t get it, and then pairing that with Remove-AppxPackage inside the user’s session for existing installs. If the users aren’t responsive, you can script it with PsExec or Intune/Endpoint Manager so it runs as them. CyberArk or admin accounts won’t bypass the fact that the app is tied to the user profile.
Another option is to use Group Policy or Intune app removal policies, which are cleaner for enterprise environments. That way you don’t have to chase down individual sessions.
So bottom line: you’re not missing permissions, you’re just fighting the user-context requirement. Use provisioned package removal for future logins, and push user-context removal via a management tool for current installs. If this clears things up, please hit “accept answer” so we know it helped and if you need more information, feel free to leave a message. We are happy to help!