Cause: If a VM was created using Admin Portal UI or using REST API with "Filter: false", the user that created the VM was never given ownership of it. Consequence: It was OK for admin users, because they can set ownership afterwards. But regular user having ReadOnlyAdmin (to give access to Admin Portal) and PowerUser permission can create VMs from Admin Portal UI, but cannot access it after that. Similar problem existed with REST API. Fix: New rule was introduced: users without admin rights are always given permission to manage the VM if they have permission to create it. Result: The behaviour has been changed only for regular users without admin rights that create VMs using Admin Portal or REST API with "Filter: false" (which is treated like usage of Admin Portal). Now they are always given ownership of the VMs they've created. In other cases the behaviour is still the same. For VMs created using User Portal or with REST API with "Filter: true" the ownership is always given to the creator - regular users and admin users are treated equally. For VMs created by admin users using Admin Portal or with REST API with "Filter: false" the ownership is not given to the creator, because admin users are typically using Admin Portal to create VMs for others.