This topic guides you to onboard an Azure Subscription (Pay as You Go) into CoreStack.
There are certain pre-requisites that need to be set up in your Azure Subscription before it can be onboarded into CoreStack.
CoreStack uses Daemon Application scenario with Client Credentials flow for OAut2.0 flow and grant type as depicted here. Client Credential flow requires a valid Application registration to be created for a specific Azure subscription to successfully allow access to the required Azure resources.
To onboard your Azure subscription into CoreStack, the following values must be generated/copied from your Azure console and configured in CoreStack.
- Tenant ID
- Application ID
- Application Secret
- Subscription Information
As you retrieve each of these values, keep them ready in a notepad to be able to copy paste into CoreStack while onboarding.
- Login to the Azure Portal (https://portal.azure.com).
- Navigate to Azure Active Directory.
- Click Properties. The Properties screen appears.
- The Tenant ID value will be displayed on the Properties screen.
- Click on the Copy icon to copy the Tenant ID.
- Navigate to Azure Active Directory > App registrations > New registration in the Azure Portal. The Register an application screen appears.
- Provide a name for the application, such as “CoreStack.App”.
The other fields can be left with the default options.
- The value of the Supported account types field can be Single Tenant.
- The value of the Redirect URI field can be blank.
- Click Register button.
The application will be registered, and the Application ID (Client ID) will be displayed in the Overview screen. Copy the Application ID.
Application Secret is the password or key that you need to provide for the specific app that was just created.
- Navigate to Certificates & secrets from the Overview screen.
- Click New client secret.
- Provide a description and expiry duration for the secret. You can leave the duration with the default value of 1 year. You can revoke this anytime later, if required.
- Click Add button. The Client secret will be created and displayed. Ensure that you copy this value since you cannot retrieve this later.
- Navigate to Subscriptions in the Azure Portal. A list of subscriptions will be listed under the selected AD Tenant.
- Select the Subscription that will be used for onboarding into CoreStack. The Overview screen appears.
- The subscription details will be displayed in the Overview screen.
- Copy the Subscription ID and Subscription Name values.
The app that is created in Step-2 must have the required access within the subscription. To provide the access, please follow the below steps:
- Navigate to Subscriptions in the Azure Portal.
- Select Access Control (IAM).
- Click + Add and select Add role assignment. Add role assignment screen appears.
- Select Contributor or Reader in the Role dropdown.
Note: Contributor role is required for subscriptions that will be onboarded with Assessment + Governance option. If the subscription will be onboarded with Assessment option, Reader role can be selected.
- Ensure that the Azure AD user, group, or service principal option is selected in the Assign access to field.
- Search and select the app that was created earlier – in this example “CoreStack.App” – in the Select field.
- Click Save button to assign the role.
Once the role is assigned, it will be listed in the Role Assignments tab.
- Repeat the steps 3 to 7 as specified above, but with Resource Policy Contributor selected in the Role dropdown and everything else remaining the same. This is required only if you intend to use CoreStack to create policies for your Azure subscription.
Note: The Resource Policy Contributor role assignment is required only if you intend to use CoreStack to create policies for your Azure subscription.
Once the role is assigned, it will be listed in the Role Assignments tab.
Copy all these details and provide them while onboarding your Azure Subscription into CoreStack.
CoreStack requires Contributor access to the following Service Providers. However, the account owner can restrict access to specific services that will only be managed through CoreStack.
Following table explains the need for access to the service with the rationale:
Reader Access (For Discovery)
Contributor Access (For Actions)
Virtual Machines Scale Sets
Virtual Machines Sizes
Network Security Group
Public IP Address
Traffic Manager Profiles
Available SSL Policy
- Preferable: Access is not mandatory. However, some of the automation features will be not functional without the required access. You can exclude them for “Assessment-Only”.
- Optional: Not mandatory, similar to that of Preferable, core features will continue to work. Some low-level actions will have an Impact. You can exclude them for “Assessment-Only”.
- Mandatory: Non-negotiable, even to onboard account with read-only permissions (“Assessment-Only”), these access details would be needed.
If you intend to use CoreStack for remediation and automation, CoreStack creates resources and applies some configurations in Azure while configuring these capabilities in CoreStack.
Alert rules will be created when monitoring thresholds are configured as part of the Operations – Alerts module.
A new alert action will be added to the created rules to invoke CoreStack notification webhook when threshold alert is triggered.
CoreStack will create the Policy Definitions and Assignments based on the GuardRails you prefer to set-up for your Azure Subscription.
CoreStack will enable the Free-tier or Standard Tier for the resources based on the security configurations. (Enabling Standard Tier has cost implications, please exercise caution during configuration).
There is no billing impact as such in configuring your account with CoreStack until certain services are consumed through CoreStack. Following are the few areas where there might be cost implications.
Free Units Included
100,000 web hooks per month
$0.60/1,000,000 web hooks
$0.10 per dynamic threshold per month
CoreStack does not create Dynamic Thresholds as part of account onboarding. However, you can configure through Operations template, if required.
Azure Security Center
Pricing varies per resource type.
Standard Tier if opted will have higher cost impact.
10 monitored metric time-series per month
$0.10 per metric time-series monitored per month
The following steps need to be performed to onboard an Azure Subscription.
- Click Add New button in the CoreStack dashboard and select Single Account.
- Click Start Now. The onboarding screen appears.
- Select Azure option in the Public Cloud field.
- Click Get Started button.
- Select the required option in the Access Type field. The options are: Assessment and Assessment + Governance.
- Select the required option in the Azure Environment field. The options are: Azure Global, Azure China, and Azure Government.
- Select the required currency in the Currency dropdown list.
- Click Next.
- Provide the details for other fields (Tenant ID, Application ID, Application Secret) as explained in the Pre-onboarding section.
- Click Validate button.
- The Advanced Settings section will be displayed with additional fields (Name, Subscription, Subscription Type, Parent Account, and Scope).
- Modify the prepopulated name of the account in the Name field, if required.
- Select the required subscription in the Subscription dropdown list.
- Select the Pay As You Go option in the Subscription Type field.
- Select the required option in the Scope field. The options are: Account, Private, and Tenant.
- Click I’m Done button.
The Azure Subscription will be onboarded successfully into CoreStack. Relevant insights and information about the resources available in the account will be populated under each cloud governance pillars in CoreStack.
Updated 11 months ago