From e47d9bd3878b5a888e5f6a92efc2a26ca0dc3dcd Mon Sep 17 00:00:00 2001 From: raj Date: Mon, 27 Jan 2025 22:35:15 +0530 Subject: [PATCH] Remove Azure management grp import --- docs/guides/azure/import/index.md | 2 +- .../azure/import/management-group/index.md | 94 ------------------- docs/guides/azure/index.md | 1 - docs/sidebar.json | 1 - 4 files changed, 1 insertion(+), 97 deletions(-) delete mode 100644 docs/guides/azure/import/management-group/index.md diff --git a/docs/guides/azure/import/index.md b/docs/guides/azure/import/index.md index a4dc9635..bcc84840 100644 --- a/docs/guides/azure/import/index.md +++ b/docs/guides/azure/import/index.md @@ -1,5 +1,5 @@ --- -title: "Connect Azure Resources to Guardrails" +title: "Connect Azure Resources" template: Documentation nav: title: "Import Azure Resources" diff --git a/docs/guides/azure/import/management-group/index.md b/docs/guides/azure/import/management-group/index.md deleted file mode 100644 index 5610226a..00000000 --- a/docs/guides/azure/import/management-group/index.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: "Import Azure Management Group into Guardrails" -template: Documentation -nav: - title: "Management Group" - order: 3 ---- - -# Import Azure Management Group into Guardrails - -[Proper setup in the Azure tenant](integrations/azure/import) is required for -import of an Azure Management Group into Guardrails. - -All child resources of the Management Group in Azure will be discovered and -subsequently entered into the Guardrails CMDB. - -While you can import an Azure Management Group at the Turbot level, it is -recommended that you import accounts into Guardrails Folders, as it provides greater -flexibility and ease of management. Define a Folder hierarchy prior to import. - -## Importing Azure Management Group via Guardrails Console - -1. At the main Guardrails screen after logging in with `Turbot/Admin` permissions, - click the purple **IMPORT** card in the top right. -2. Select **Azure Management Group** on the left. -3. Use the **Parent Resource** dropdown menu to select where the Azure - Management Group will be imported to. -4. Enter the **Management Group ID**, **Tenant (directory) ID**, **Client - (application) ID**, and **Client Key (secret)**, as well as the - **Environment** type then click **Import**. -5. Congratulations! The management group is now added as a child resource of the - folder. - -CMDB and Discovery controls are enabled by default and Guardrails will begin -discovering the resources in the Azure Management Group. Resources will start -appearing right away, and resource discovery will continue to run in the -background. - -## Management Group Event Pollers - -Guardrails uses Management Group event pollers to detect new, updated or deleted subscriptions in the -management group. Management Group event pollers are enabled by default. No action is required. - - -## Import Management Group via Terraform - -Administrators can easily import Management Group using Terraform. If your -Terraform environment has not been setup, head on over to the -[Terraform Setup Page](reference/terraform/setup). - -```hcl -# Create the Azure > Management Group resource in Guardrails -resource "turbot_resource" "management_group_resource" { - parent = var.parent_resource - type = "tmod:@turbot/azure#/resource/types/managementGroup" - akas = ["azure:///tenants/${var.azure_tenant_id}/microsoft.management/managementgroups/your management group id"] //highlight-line - metadata = jsonencode({ - "azure" : { - "tenantId" : "your tenant id" //highlight-line - "managementGroupId" : "your management group id" //highlight-line - } - }) - data = jsonencode({ - "id" : "/providers/Microsoft.Management/managementGroups/your management group id" //highlight-line - "name" : "your management group id", //highlight-line - }) -} - -# Set the credentials for the Management Group via Guardrails policies - -resource "turbot_policy_setting" "environment" { - resource = turbot_resource.management_group_resource.id - type = "tmod:@turbot/azure#/policy/types/environment" - value = "Global Cloud" or "US Government" //highlight-line -} - -resource "turbot_policy_setting" "clientKey" { - resource = turbot_resource.management_group_resource.id - type = "tmod:@turbot/azure#/policy/types/clientKey" - value = "turbot application client key" //highlight-line -} - -resource "turbot_policy_setting" "clientId" { - resource = turbot_resource.management_group_resource.id - type = "tmod:@turbot/azure#/policy/types/clientId" - value = "turbot application client id" //highlight-line -} - -resource "turbot_policy_setting" "tenantId" { - resource = turbot_resource.management_group_resource.id - type = "tmod:@turbot/azure#/policy/types/tenantId" - value = "your tenant id" //highlight-line -} -``` diff --git a/docs/guides/azure/index.md b/docs/guides/azure/index.md index 1ae13f55..de69d573 100644 --- a/docs/guides/azure/index.md +++ b/docs/guides/azure/index.md @@ -28,7 +28,6 @@ Turbot Guardrails is deeply integrated with - [Import Azure Tenant](integrations/azure/import/tenant) - [Import Azure Active Directory](integrations/azure/import/active-directory) - - [Import Azure Management Group](integrations/azure/import/management-group) - [Import Azure Subscription](integrations/azure/import/subscription) 2. [Enable Azure Services](integrations/azure/services) that you will use diff --git a/docs/sidebar.json b/docs/sidebar.json index bbe035d2..25ff0907 100644 --- a/docs/sidebar.json +++ b/docs/sidebar.json @@ -235,7 +235,6 @@ "items": [ "guides/azure/import/tenant", "guides/azure/import/active-directory", - "guides/azure/import/management-group", "guides/azure/import/subscription" ] },