Feature Overview

The CoreStack Onboarding Hub (onboard.corestack.io) is the entry point for connecting AWS, Azure, and GCP cloud accounts to the CoreStack platform. Once an account is onboarded, CoreStack can bring it under FinOps, CloudOps, Assessments, and SecOps capabilities. This guide is intended for Customer Success, Professional Services, and Cloud Operations teams onboarding customer or internal cloud accounts.

This guide covers every onboarding path currently available in the Hub:

• Single Account Onboarding — onboard one Azure subscription at a time using an interactive Azure sign-in to discover accessible subscriptions.
• Bulk Onboarding — onboard many accounts, subscriptions, or projects in one pass, for AWS, Azure (EA, MCA, or CSP), and GCP.

How It Works

The Onboarding Hub is the landing page after login and offers the two onboarding paths above. A "Need Help?" panel at the bottom of the Hub links to internal documentation and support for any issues encountered during onboarding.

Prerequisites

Before you begin, ensure the following:

• CoreStack access: Active login credentials with access to the Onboarding Hub.
• Account Master & Tenant: Know the correct Account Master and Tenant to onboard the subscription or accounts under.
• Modules: Decide which CoreStack modules to enable — FinOps, CloudOps, Assessments, SecOps.
• Access level: Decide whether onboarding needs Read Only or Read Write access.

Logging In

1. Navigate to https://onboard.corestack.io/ in your browser.
2. In the Environment URL field, enter your CoreStack environment without the "https://" prefix, for example xxxxx.corestack.io.
   • Username & Password — enter your Username/Email and Password, then select Log in.
   • API Key & Secret — enter the API Key and Secret issued for the environment, then select Log in.
3. On successful authentication, the Onboarding Hub is displayed.

The Onboarding Hub

The Onboarding Hub is the landing page after login and offers two onboarding paths.

A "Need Help?" panel at the bottom of the Hub links to internal documentation and support for any issues encountered during onboarding.

Single Account Onboarding (Azure — Interactive Login)

This path onboards one Azure subscription at a time. You sign in interactively to Azure (via a device login code) so CoreStack can discover the subscriptions your account can access, then complete onboarding with an existing App Registration's credentials. Use this when you want to browse and confirm available subscriptions through your own Azure sign-in before committing App Registration details.

Before You Start

Procedure

Step 1 — Open Single Account Onboarding

From the Onboarding Hub, click Go to Single Onboarding under the Single Account Onboarding card.

Step 2 — Select Account Master, Tenant, and Azure

1. Under Select Account Master, choose the relevant account master (e.g., admin.psteam).
2. Under Select Tenant, choose the target tenant.
3. Select the Azure tile from the cloud provider options (AWS / GCP / Azure).

Step 3 — Choose Individual Subscription Onboarding

The Azure Configuration panel opens with a single onboarding type. Click Individual subscription onboarding to onboard one Azure subscription at a time.

Step 4 — Start Azure interactive login

Click Start Azure Interactive Login to begin device-code authentication. A new browser tab opens to Microsoft's sign-in page.

Step 5 — Complete the device login sign-in

1. In the new tab, confirm the device code shown on the CoreStack page matches the one displayed, then sign in with Azure credentials that have access to the target subscription(s).
2. When prompted "Are you trying to sign in to Microsoft Azure CLI?", verify the account shown and click Continue.
3. Once Microsoft confirms sign-in was successful, close the browser tab and return to CoreStack.

Step 6 — Select the subscription(s) to onboard

An "Azure Login Successful!" banner appears with the list of subscriptions the signed-in account can access. Already-onboarded subscriptions are labeled accordingly.

1. Check Select All, or choose specific subscriptions to onboard.
2. Click Continue Onboarding. Use Clear Token and Login Again to sign in with a different Azure account.

Step 7 — Enter the Azure Onboarding Configuration

Provide the App Registration details for the Service Principal that will grant CoreStack ongoing access. Fields marked with a red asterisk (*) are required.

• App Registration ID and Tenant ID — from your Azure AD App Registration.

• Object ID — the Object ID of the Service Principal (not the App Registration's own object ID).

• Secret Key — the client secret value for the App Registration.

• Currency — the billing currency, e.g., USD - US Dollar.

• Access Type — Read Only for visibility-only access, or Read Write if CoreStack must also perform remediation/automation.

  

  ⚠️

  Important: Double-check the App Registration ID, Tenant ID, Object ID, and Secret Key before submitting — incorrect values will cause onboarding or role assignment to fail.

Step 8 — Select modules and onboard

1. Under Select Module(s), check Select All, or individually check FinOps, CloudOps, Assessments, and/or SecOps.

2. Click Onboard Cloud Accounts to submit.

   

   📘

   Note: Role assignment and propagation on the Azure side can take several minutes. Avoid resubmitting the form while onboarding is in progress.

Step 9 — Review the onboarding results

CoreStack displays the status of each selected subscription, with counts for Onboarded, already onboarded, and failed.

Step 10 — Onboard any remaining subscriptions

If the signed-in account has access to additional subscriptions that weren't selected initially, they can be onboarded in the same session:

1. Click Select not onboarded subscriptions to return to the subscription list.
2. Check the additional subscription(s) — already-onboarded ones are highlighted and labeled Onboarded.
3. Click Continue Onboarding and repeat Steps 7–9 (configuration, module selection, and review) for the newly selected subscriptions.

Bulk Onboarding

Bulk Onboarding connects multiple accounts, subscriptions, or projects in a single pass, under one set of credentials. It supports AWS, Azure (EA, MCA, and CSP), and GCP.

Common Setup

From the Onboarding Hub, select Go to Bulk Onboarding. The steps below are shared across all cloud providers before you reach provider-specific configuration.

1. Select Account Master — choose the CoreStack account master under which the cloud accounts will be onboarded (pre-populated based on login context).
2. Select Tenant — choose the CoreStack tenant the billing accounts belong to.
3. (Optional) Check Onboard to different tenant to onboard into a tenant other than the one selected, then choose it from the Select Different Tenant dropdown.
4. Select the target cloud provider tab: AWS, Azure, or GCP.

AWS

1. Select AWS Management Account from the dropdown (required).
2. Choose the Onboarding Type: Read or Read-Write.
3. Enter the Role Name and External ID (required).
4. Under Select Product(s), check the CoreStack modules to enable: FinOps, CloudOps, Assessments, SecOps (or Select All).
5. Select List Child Account to retrieve the list of AWS accounts available under the management account.
6. In the resulting account table, check the accounts to onboard (or Select All), then select Onboard Now.

Azure — EA and MCA Subscriptions

Selecting the Azure tab first presents an Azure Onboarding Options chooser:

The steps below cover the EA path (selected by default in most PS tenants); MCA follows an equivalent flow with MCA-specific fields.

1. Select Onboard Azure EA Subscriptions. Use the × in the panel header to return to the chooser if a different option is needed.
2. Select the Azure EA Parent Account (shows the Enrollment ID).
3. Choose the Onboarding Type: Read or Read-Write.
4. Enter the Tenant ID, Application ID, and Application Secret for the Azure App Registration used for EA access.
5. Under Select Product(s), check the desired CoreStack modules (FinOps, CloudOps, Assessments, SecOps) or Select All.
6. Select List EA Subscriptions to load the Azure EA Subscriptions table.
7. In the table, use Search by name or subscription ID if needed, then check the subscriptions to onboard (or Select All Azure EA Subscriptions). Account names are editable inline via the pencil icon before onboarding.
8. Review the Status column for each subscription (e.g., Failed indicates a previous onboarding attempt did not succeed) and use pagination to review all results.
9. Select Onboard Now (n subscriptions selected) to onboard the checked subscriptions.

Azure — CSP Subscriptions

This path is used to onboard subscriptions belonging to Azure CSP (Cloud Solution Provider) end-customers, in bulk, in a single session.

1. Under Azure Onboarding Options, click Onboard Azure CSP Subscriptions.

   

2. In the Azure CSP Configuration dialog, select the Azure CSP Parent Account — the CSP partner (parent) account under which the customer sits.
3. Select Customer — the specific end-customer whose subscriptions you are onboarding.
4. Choose the Onboarding Type: Read (monitoring/visibility-only) or Read-Write (remediation/automation).
5. Enter the Tenant ID and Application ID from your Azure AD App Registration.
6. Enter the Application Secret (client secret value) for that App Registration.
7. Under Select Product(s), check Select All or the individual modules to enable.
8. Click List CSP Subscriptions to validate the credentials and retrieve the available subscriptions for the selected customer.

9. Review the Azure CSP Subscriptions list, showing Account Name, Subscription ID, Tenant, and Status.
10. Check Select All Azure CSP Subscriptions to onboard every listed subscription, or check individual rows for a subset. Use the search bar to find a subscription by name or ID if the list is long.
11. Optionally, click the pencil icon next to any Account Name (Editable) field to rename the subscription as it will appear in CoreStack.
12. Click Onboard Now — the button label shows the number of subscriptions selected, e.g., "Onboard Now (2 subscriptions selected)".

GCP

1. Under GCP Onboarding Options, choose GCP Projects (Linked to Billing Account) or GCP Projects (Linked to Organization) — the Organization option is only enabled when the relevant organization-level connection is available.
2. Select List Billing-Linked Projects (or the equivalent for the Organization option) to retrieve the eligible GCP projects.
3. Select the projects to onboard and select Onboard Now.

Frequently Asked Questions

Q: What's the difference between Single Account Onboarding and Bulk Onboarding, and which should I use?

Use Single Account Onboarding when you want to onboard one Azure subscription at a time and confirm which subscriptions your Azure sign-in can access before entering App Registration details. Use Bulk Onboarding when you're onboarding many accounts, subscriptions, or projects in one pass under a single set of credentials — for AWS, Azure (EA, MCA, or CSP), or GCP.

Q: Can I use Single Account Onboarding for AWS or GCP?

No. Single Account Onboarding is Azure-only and uses an interactive Azure sign-in. To onboard AWS accounts or GCP projects, use Bulk Onboarding and select the AWS or GCP tab.

Q: What does it mean if a subscription or account shows as "already onboarded"?

It means that subscription or account is already connected to CoreStack under the tenant you selected. You can still select it again — CoreStack will indicate its existing status in the results — but re-onboarding an already-connected account isn't necessary. [VERIFY: confirm whether re-selecting an already-onboarded subscription re-runs onboarding or is a no-op.]

Q: Should I choose Read Only or Read Write access?

Choose Read Only if CoreStack only needs visibility into the account for monitoring and reporting. Choose Read Write if you also want CoreStack to perform remediation or automation actions on the account. [VERIFY: confirm whether access type can be upgraded from Read Only to Read Write later without re-onboarding.]

Q: Can I change which modules (FinOps, CloudOps, Assessments, SecOps) are enabled after onboarding?

This isn't covered in the onboarding flow itself. [VERIFY: confirm the correct place to change enabled modules after initial onboarding — for example, via account settings — and update this answer accordingly.]

Troubleshooting

An account or subscription shows a "Failed" status after onboarding

Cause: This is typically caused by incorrect credentials (App Registration ID, Tenant ID, Object ID, Secret Key for Azure; Role Name/External ID for AWS; Tenant ID/Application ID/Secret for CSP), insufficient permissions on the role or Service Principal, or the role assignment still propagating on the provider side.

Solution:

1. Re-check the credential fields you entered against the values in your Azure App Registration, AWS IAM role, or CSP App Registration — the guide's Important callouts flag these as the most common source of failures.
2. If the failure appeared shortly after submitting, wait a few minutes for role assignment/propagation to complete before retrying, rather than resubmitting immediately.
3. For Single Account Onboarding, use Select not onboarded subscriptions to return to the list and retry the failed subscription(s).

If the issue persists, contact CoreStack support with the subscription/account ID, the cloud provider, the onboarding path used (Single or Bulk, and which tab), and the exact status/error shown.

The Azure interactive device login doesn't complete

Cause: The device code wasn't confirmed correctly, the wrong Azure account was used to sign in, or the browser tab was closed before Microsoft confirmed the sign-in.

Solution:

1. Restart the flow with Start Azure Interactive Login and confirm the device code shown on the CoreStack page matches the one on Microsoft's sign-in page before entering credentials.
2. When prompted "Are you trying to sign in to Microsoft Azure CLI?", verify the account shown is the one with access to your target subscription(s) before clicking Continue.
3. Wait for Microsoft to confirm sign-in was successful before closing the browser tab and returning to CoreStack.

If sign-in keeps failing with the correct account, contact CoreStack support with the Azure account used and approximately when the attempt was made.

"List [Child Account / EA Subscriptions / CSP Subscriptions]" returns no results or an error

Cause: The Tenant ID, Application ID/App Registration ID, or Secret entered doesn't match the App Registration, or that App Registration/IAM role doesn't have the permissions needed to enumerate accounts or subscriptions. [VERIFY: confirm the exact permission requirements for the listing calls to succeed.]

Solution:

1. Double-check the Tenant ID, Application/App Registration ID, and Secret against the values in Azure AD or AWS IAM — the guide's Important callouts note that incorrect values here cause the lookup to fail.
2. Confirm the App Registration or IAM role was created against the correct tenant, management account, or CSP partner tenant.
3. Retry the List action (List Child Account / List EA Subscriptions / List CSP Subscriptions) after correcting the credentials.

If the list still comes back empty or errors, contact CoreStack support with the Tenant ID / Management Account ID used, the onboarding path (AWS, Azure EA/MCA, or CSP), and the exact error message.