Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for IAM
    • Fixing errors when assigning the resource-manager.clouds.owner role to the Yandex Cloud user
    • Fixing errors related to invitations to a cloud organization
    • Fixing errors when adding a new user to a cloud organization
    • Fixing the "The signature of response or assertion was invalid" error when authorizing by a federated account
    • Resolving Issues when creating OAuth tokens on behalf of Yandex ID accounts
    • Resolving Issues when transferring a cloud between organizations
    • Resolving the "OAuth token is invalid or expired" error
    • Resolving the "Contact your organization's administrator for a new invitation" error
    • Resolving the "Service account is not available" error
    • Deleting a cloud
    • Canceling cloud deletion
    • How to change the cloud owner
    • How to change the organization owner

In this article:

  • Issue description
  • Solution
  1. IAM
  2. Resolving Issues when transferring a cloud between organizations

Resolving Issues when transferring a cloud between organizations

Written by
Yandex Cloud
Updated at November 27, 2023
  • Issue description
  • Solution

Issue descriptionIssue description

When transferring a cloud between different organizations, you see this error message: publicAccessBindings.

SolutionSolution

This error arises due to a mismatch in the user list between the source and new organizations.
During the transfer, the system tries to maintain existing rights for the cloud, but fails to do this because users from the old organization do not have membership or proper rights for the new one.

You can choose one of the options:

  1. Remove these users' rights to the ump-group cloud and transfer the cloud to the new organization
  2. Add the users to the new organization and then move the cloud.

Was the article helpful?

Previous
Resolving Issues when creating OAuth tokens on behalf of Yandex ID accounts
Next
Resolving the "OAuth token is invalid or expired" error
© 2025 Direct Cursus Technology L.L.C.