Unmanaging an Account
Function
This API is used to cancel the RGC management of an organization account.
Authorization Information
Each account root user has all the permissions required to call all APIs, but IAM users must be assigned the following required identity policy-based permissions. For details about the required permissions, see Permissions Policies and Supported Actions.
Action | Access Level | Resource Type (*: required) | Condition Key | Alias | Dependencies |
|---|---|---|---|---|---|
rgc:managedAccount:unEnroll | Write | - | - | - | - |
URI
POST /v1/managed-organization/managed-accounts/{managed_account_id}/un-enroll
Parameter | Mandatory | Type | Description |
|---|---|---|---|
managed_account_id | Yes | String | ID of an enrolled account. |
Request Parameters
None
Response Parameters
Status code: 200
Parameter | Type | Description |
|---|---|---|
operation_id | String | Operation ID for creating an account, enrolling an account, or registering an OU. |
Status code: 403
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code. |
error_msg | String | Error message. |
request_id | String | Unique ID of the request. |
encoded_authorization_message | String | Encrypted error message. |
details | Array of ForbiddenErrorDetail objects | Error message indicating no permissions for cross-service invoking. |
Example Requests
Canceling the RGC management of an organization account
POST https://{endpoint}/v1/managed-organization/managed-accounts/{managed_account_id}/un-enroll Example Responses
Status code: 200
Request succeeded.
{
"operation_id" : "string"
} Status Codes
Status Code | Description |
|---|---|
200 | Request succeeded. |
403 | No permissions. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
