Using Bill-Splitting to Assign Costs to Child Organizations
Note:See Managing Child Organizations for information on creating child organizations for your customers. You must have these child organizations created prior to performing bill-splitting steps.
Role Requirements
The following roles are required to perform bill-splitting.
Role Name |
Description |
Manage organization |
Full access to all organization capabilities. This role is used for all actions that require an org-level administrator. For complete descriptions of each role available in Flexera One, see Flexera One Roles. |
Manage cloud |
Full access to all features and functionality in Cloud Cost Optimization. This role has all available permissions relative to Flexera One Cloud Cost Optimization features within the organization. For complete descriptions of each role available in Flexera One, see Flexera One Roles. |
Supported Vendors
Bill-splitting is supported for the following cloud vendors:
• | Amazon Web Services (AWS) |
• | Azure Enterprise Agreement (EA) |
• | Azure Modern Commerce Agreement (MCA) |
• | Google Cloud Platform (GCP) |
Bill-Splitting Sections
The following table describes the instructions, explanations, and reference information contained in this section.
Important:Bill connects and bill-splitting must be performed within your parent organization. It cannot be done from within your customers’ child organizations.
Section |
Description |
Discusses the bill-splitting concepts and steps at a high level. |
|
Describes how to create a bill connect to ingest your billing data. |
|
Describes how to use rule-based dimensions to allocate billing data from different vendor accounts to the appropriate child organization. |
|
Describes how to use the Flexera One dashboard to confirm bill-splitting configurations in the Flexera One UI. |