How do I remove a linked account from an organization?

Navigation Menu: Customers

Overview: This article provides detailed information on how to remove, suspend or delete accounts or subscriptions from SIE.

Important! Please do not delete accounts from SIE so that historical billing data can be preserved and final invoicing can be completed. Please follow the instructions for unlinking or removing AWS accounts from the current Organization, or submit a support ticket to request the suspension of an Azure subscription.

There are multiple scenarios to be considered and different rules defined by the cloud provider.  Instructions for each are provided later in this article.  In this article, we cover the following topics:

1. Deleting a cloud account from a customer account list (not cloud vendor specific)
2. Unlinking an AWS account from a TDS managed master payer.  Unlinking means requesting to stop the billing within SIE via TDS.  In order to send the invoicing responsibility back to AWS, advise the account owner to Unlink the account from our consolidated payer. If the account owner is unable to unlink the account from AWS, please submit a support ticket in SIE.

For Microsoft Azure Accounts or Subscriptions, the options are:

1. Transfer the account to another CSP
2. If the subscription (or account) is no longer needed, the subscription can be "suspended".  To suspend an active subscription, please submit a support ticket in SIE.

Removing from the Consolidated AWS Payer in the AWS Console (Unlinking from Organization)

Customers with root access to their AWS account can Unlink their AWS account from our Organization at any time using the AWS interface, without the need for help from a reseller or the SIE Ops team. Here are the procedures for removing a linked account that you can share with your customer:

To leave an organization as a member account:

1. Sign in to the AWS Organizations console at AWS Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user in a member account.
   By default, you don't have access to the root user password in a member account that was created using AWS Organizations. If required, recover the root user password by following the steps at Accessing a member account as the root user.
2. On the Organizations Dashboard page, choose Leave organization.
3. Perform one of the following steps:
   • If your account has all the required information to operate as a standalone account, a confirmation dialog box appears. Confirm your choice to remove the account. You are redirected to the Getting Started page of the AWS Organizations console, where you can view any pending invitations for your account to join other organizations.
   • If your account doesn't have all the required information, perform the following steps:
     1. A dialog box appears to explain that you must complete some additional steps. Click the link.
     2. Complete all the sign-up steps that are presented. They might include the following:
        • Provide contact information (including contact name and address)
        • Provide a valid payment method
        • Verify the phone number
        • Select a support plan (optional)

     3. When you see the dialog box stating that the sign-up process is complete, choose Leave organization.
     4. A confirmation dialog box appears. Confirm your choice to remove the account. You are redirected to the Getting Started page of the AWS Organizations console, where you can view any pending invitations for your account to join other organizations.

4. Remove the IAM roles that grant access to your account from the organization.

Important! To unlink an account from a consolidated payer, you must have a valid payment method on file. AWS will not allow accounts to be removed from payer accounts if it doesn't have a credit card on file. 

*Notes about Member accounts under an AWS Organization.  An account’s status with an organization affects what cost and usage data is visible:

• When a standalone account joins an organization, the account no longer has access to cost and usage data from the time range when the account was a standalone account.
• If a member account leaves an organization and becomes a standalone account, the account no longer has access to cost and usage data from the time range when the account was a member of the organization. The account has access only to the data that is generated as a standalone account.
• If a member account leaves organization A to join organization B, the account no longer has access to cost and usage data from the time range when the account was a member of organization A. The account has access only to the data that is generated as a member of organization B.
• If an account rejoins an organization that it previously belonged to, the account regains access to its historical cost and usage data.

For AWS accounts owned by the Customer (not requested through platform) the work flow is as follows:

• End User customer notifies the Reseller of their intent to remove their account
• Reseller shall notify the TDS SIE team and provide the AWS account number(s) to be removed.
• SIE Support Operations will remove the account(s) from the AWS payer account.  

The account separation takes effect immediately and the linked account owner is billed for AWS services account moving forward. If the separation occurs somewhere in the middle of the month, as the Reseller you will invoice the customer for only for the time period the account was linked.

AWS Dedicated Payer Accounts (Root Access not owned by End Customer)

For AWS accounts created through AWS Organizations under a TDS-owned payer   

The process to release the accounts requires additional steps. The work effort to separate from the program is as follows:

• End User customer notifies the Reseller of their intent to remove their account
• Reseller shall notify the SIE (Sale or Support) and provide the AWS account number(s) to be removed.
• Support sends and email requesting the following details.  These will be contact information for the company to whom Tech Data is transferring the account to:

        Company:                       

        Contact Name:                       

        Address:                       

        City:                      

        State:                       

        Postal Code:                       

        Country
                       

        Billing Contact Name:                      

        Billing Contact Phone:                       

        Billing Contact email address:
        Email Address where account assignment can be sent:    

Upon receipt of the information, the SIE Support team contacts AWS to start the transfer of ownership.  The transfer process removes Tech Data's financial and contractual obligations for the AWS account and assigns it to the new owner.  During this process the payment method and terms are updated in the AWS account.

When the paperwork is complete, SIE support provides the credentials for the account directly to the new owner and 

removes the account from the consolidated payer.

SIE Support operations notifies the you when the transfer is complete.

Closing an AWS account

Closing an AWS account can be by the Root account owner only.  Please follow the instructions on the AWS website to close an account.  

The following steps are used to delete a cloud account from SIE:

Log in to the platform management console

Select the [Customer] module

Select a Client from the list, click [Edit] 

Select the 'Cloud accounts' menu option.

From the Cloud Accounts screen, select the account you want to remove. The Cloud Account window displays.

Click [Delete] then click [OK] to confirm

Figure 1 - Sample Delete account process

Deleting a Customer Account or Customer Profile

The platform protects certain data from being removed.  One of them may be a customer profile that has historical billing data associated to it.  If you use the [Delete] feature from the Customer billing module you may receive this message:

Figure 2 - Sample message for deleting a Customer Profile

A message is sent to the platform operations team to approve the request for Customer profile deletion.  This request may or may not be approved.  

Figure 3 - Sample Customer Module with pending approval to delete a Customer profile

If approved, ALL current and historical billing data is removed from SIE; unless you have generated billing statements in the platform which retains the historical information.

Any account with current month or spend within the last 2 years will not be approved.  Please contact support if you need assistance with Unlinking or if you have Deleted an account in error.***