Deployed Resources

Import live Azure resources into Clophi, edit their full configuration, and deploy, duplicate, or export them as Infrastructure-as-Code.

Overview

Clophi can fetch any deployed Azure resource, along with its child resources. You get the complete configuration into an intelligent form. From there, you can modify the resource, duplicate it to a different scope, or use it as the starting point for new infrastructure.

Resource forms are generated from the official ARM reference schemas. That means every available property for a resource type is available in the form. This includes properties that the Azure Portal does not surface in its UI.

Common use cases

ConfigureAdjust resource properties that are not exposed in the Azure Portal interface.
Duplicate resourceCopy a deployed resource "as is" into a different subscription, resource group, or region.
Duplicate IaCGenerate Infrastructure as Code of your resources in another format (Terraform, Bicep or Arm Template).
Create InfrastructureBuild new infrastructure projects using your existing resources as the foundation.

Granting access

Clophi needs read access to the resources it will fetch. Assign the Clophi reader service principal the Reader role on the resource groups you want to access, or at the subscription scope for broader coverage.

Importing a Resource

Select a resource from the resource list to view its details. If the resource has child resources, they are listed in the right tab where they can be selected individually.

Choose the API version you want to use for the import, then click Import Resource. Clophi fetches the resource configuration and loads it into an editable resource form.

Resource list with child resources tab and API version selector — Selecting a resource exposes its child resources and an API version selector for import.

Editing the Resource

Once imported, the resource configuration appears in the resource form. Every property defined by the ARM schema is editable here and comes with detailed documentation and guidance. Each field has a filter that permits only allowed values as well.

Resource form for modifying configuration

Sensitive values are not fetched

For security reasons, Clophi does not retrieve sensitive properties such as administrator passwords, access keys, or connection secrets. These fields are empty in the resource form and must be filled in manually before deployment.

When you've finished editing, click Add to Infrastructure to include the resource in your current infrastructure project.

Building a Collection

You're not limited to a single resource. Repeat the import process to add multiple resources to your infrastructure, drawing from any resource group or subscription.

Deploying or Exporting

Once your infrastructure project is assembled, you have three ways to act on it from the Infrastructure section.

Deploy directly from Clophi

Clophi can deploy your infrastructure to Azure on your behalf using the Clophi deployer service principal.

Required permission

To deploy directly, the Clophi deployer service principal must have write permissions on the target scope (subscription or resource group). The Contributor role is typically sufficient, but any role granting write access to the relevant resource types will work as well. Without adequate permissions, deployments will fail.

Download as Infrastructure-as-Code

Export your infrastructure as code in your preferred format: Terraform , Bicep, or ARM Template. Each format is available in parameterized or non-parameterized structure.

Push to your repository

Alternatively, you can push your generated infrastructure code directly to a connected Git repository. Select your preferred branch, IaC format, and parameterization mode. Clophi commits the code and opens a pull request.