---
title: ALC
slug: blueprint/alc
createdAt: 2026-06-19T16:23:35.499Z
---

The ALC area has the following settings:

- **Enable Flow Activity Tracking** — Enables tracking of PAD flow run history and activity data in Blueprint
- **Enable PAD Log** — Enables PAD log collection within Blueprint
- **Enable Dataverse Synchronization** — Enables synchronization between Blueprint and Dataverse. When enabled, configure the following:
  - **[Dataverse Service Account Secret Setup](docId\:BE2S_hdbzuaUDe3PLfQ3E)** — The secret key used to authenticate the Dataverse service account
  - **Synchronization Interval (in minutes)** — How frequently Blueprint syncs with Dataverse

    :::hint{type="info"}
    Dataverse Synchronization and Service Account Secret are required for:

    - Identifying PAD flows that have been updated post import to Blueprint
    - Monitoring automated Test Runs
    - Monitoring Flow Activity
    - Logs
    :::
- **Blueprint Versioning** — Versions are created and managed within Blueprint
- **Microsoft Versioning** — Versions follow Microsoft's versioning model from the Power Platform environment

:::hint{type="warning"}
⚠️ Switching versioning modes changes how new versions are created and which versions are visible. Blueprint will only show versions created under the active mode. Previously created versions are retained in the database but will not be visible unless you switch back to that mode.
:::

# Environments for ALC

ALC can work with multiple Power Platform environments. An administrator chooses which environments ALC connects to, then applies a template to each one to control which ALC features are available in it.

## Before You Begin

- A [Microsoft Connection](docId\:ZoxcTj3VK7aGp9feDw-Te) must be configured
- ALC uses one service account for every environment. The Power Automate Desktop settings in **Settings -> RPA Management -> Analyze -> Power Automate Desktop** apply to each environment you add
- That service account must exist in every environment you want to add. Blueprint checks for it and won't add an environment where it's missing

## Environment Template

A template defines which ALC features are enabled in an environment. Every environment uses all ALC features unless you apply a template.

To create an environment template:

::::WorkflowBlock
:::WorkflowBlockItem
Click the "Add Environment Template" button
:::

:::WorkflowBlockItem
Enter a name for the template, and brief description, then click "Add Environment Template"
:::

:::WorkflowBlockItem
Click the pencil icon in the last column to launch the feature picker
:::

:::WorkflowBlockItem
Select desired features for the template, then click Select
:::
::::

## Environments

To Add an environment that will be availble in ALC:

::::WorkflowBlock
:::WorkflowBlockItem
Click the "Add Environment" button
:::

:::WorkflowBlockItem
Choose one or more available environments, and click "Add Environments"
:::

:::WorkflowBlockItem
Optionally click the pencil icon in the Template column, and choose a template
:::
::::

## Environments Table



| **Column**             | **Description**                                                                          |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| **Name**               | The environment's name in Power Platform                                                 |
| **Template**           | The environment template applied to this environment. Click the pencil icon to change it |
| **Service Account**    | Whether a service account is configured for this environment in Power Platform           |
| **Server Time Zone**   | Time Zone of the server                                                                  |
| **Default Recipients** | Add default recipients to Flow Activity monitoring                                       |