...
To obtain Azure CSP credentials, do the steps at: Obtain Azure ARM pricing credentials for CSP
In Abiquo, edit the reseller enterprise
Go to Credentials → Pricing, and add the Azure CSP pricing credentials as follows
API key:
csp#tenantId#clientId#accessToken#refreshToken
API secret key: the password for the application
Go to Properties, and to use Azure billing, enter the billing enterprise properties in the reseller enterprise. The default values are as follows:
azurecompute-arm_discount = 0
azurecompute-arm_currency_code = USD
billing.azure.country_code = US
azurecompute-arm_price_factor = 1 (deprecated in Abiquo 6.1)
For Abiquo 6.1 and above, go to Pricing → Price factors and create a price factor for the reseller enterprise. See Manage price factors.
...
4. Onboard an AWS organization
Log in to the AWS management account.
Create a user with the security policy for AWS organization pricing
Edit the Abiquo reseller enterprise:
Go to Credentials → Pricing and add the user credentials
Go to Properties and add AWS enterprise properties to the reseller
For Abiquo 6.1 and above, go to Pricing → Price factors and create a price factor for the reseller enterprise. See Manage price factors.
...
5. Prepare Abiquo entities to onboard a customer
You can create a tenant hierarchy with a reseller scope at the top level and the customers below that. To create customers of your reseller, for each customer, create a customer scope and set the reseller scope as the parent scope.
...
Create a customer scope:
Go to Users → Scopes and click the + add button or select and edit an existing scope
For the Name, we recommend that youuse the customer name and
Scope
, for example,Customer1Scope
For the Parent scope, select the reseller scope, for example,
ResellerScope
.
For the Entities, select the public cloud region/s.
Create a customer enterprise:
Go to Users view and at the bottom of the Enterprises list, click the + add button
For the Default scope, select the customer scope, for example,
Customer1Scope
Select the Key node checkbox to support
Office365 customers
Multiple Azure subscriptions (Plans)
Other sub-tenants (e.g. AWS partner accounts)
For Properties,add tenant metadata as required. This may include account IDs and discounts. You can also push this metadata to VM variables but do not use confidential data.
For each subscription in an Azure plan, create a standard enterprise (subtenant):
Create a standard enterprise (not a key node)
For the Default scope, select the
Customer1Scope
...
...
6. Onboard an Azure CSP customer
You can onboard a CSP customer with access to compute and billing features or with access to billing only. If your CSP customer is working with Azure plans, then add credentials for each subscription within the Azure plan to a separate Abiquo enterprise.
...
To give a CSP customer access to compute and billing features:
Create an app in the customer’s Active Directory.
Edit the standard enterprise, and go to Credentials → Public
Add the credentials for customer in the format
Subscription#AppID#TenantID
Go to Properties and add
azurecompute-arm_only_bill_subscription
and set the value totrue
...
Edit the standard enterprise, and go to Credentials → Public
For the Access key ID, enter the customer’s subscription details in this format:
Subscription##TenantID
For the Secret access key, enter any value
Select Only for billing
Click Add account to save the credentials. The platform will not validate the account details until it retrieves billing data from the provider
Go to Properties and add
azurecompute-arm_only_bill_subscription
and set the value totrue
Click Save
Now you can configure the MicrosoftProductsService to manage Customer users, office licenses and Azure plan subscriptions!
...
7. Onboard an account under an AWS organization
To onboard an account under an AWS organization:
Create a customer scope under the reseller scope
Create a key node enterprise in the customer scope
Create a standard enterprise in the customer scope
Log in to AWS and in the customer account, create a user
In Abiquo, edit the standard enterprise and add the credentials as public cloud credentials.
OR Add the account to the standard enterprise as billing only public cloud credentials.
...