Skip to main content
Table of Contents

Analyze

This article explains how to access and configure Blueprint Analyze settings within the Blueprint Assess interface, including tool-specific toggles for Power Automate Desktop, UiPath, and Blue Prism. It details general thresholds, Dataverse synchronization parameters, GenAI options, and PAD-only authentication requirements. Administrators can fine-tune analysis behavior, alerting, and AI-driven features to match their organization’s RPA estate.

Stefenie Stockbridge
Updated by Stefenie Stockbridge

These settings within RPA Management -> Analyze allow you to configure features and behavior of the four Analyze areas of the product.

Analyze Settings

Integration Options

Enable RPA Tool – Enable or disable the Analyze features for each of the supported RPA tools: Power Automate Desktop, UiPath, Blue Prism, and Automation360.

General Settings

Cloudability Threshold - adjust the threshold for designating a process as "cloudable"

Power Automate Desktop

  • Enable Solution Imports & Metrics – Allows for import of PAD solution files to Analyze - PAD
  • Enable Flow Activity Tracking – Enables operational analytics of in production PAD flows.
  • Enable Dataverse Synchronization –
    • Service Account Secret - Configure import of updated flows (see Dataverse Service Account Secret Setup).
    • Synchronization Interval (in minutes) - Defines how often Blueprint should check the connected PAD environment for updated Flow data.
    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
  • Anomaly Alert Timeframe – Define how long high-risk flows are flagged.
  • Versioning Types – Blueprint supports two versioning types for the Changes feature: Blueprint Versioning and Microsoft Versioning. The type you choose determines how and when flow versions are captured and stored.
    • Blueprint Versioning:
      • Blueprint Versioning works with both Solution File imports and Dataverse imports
      • Versions are stored indefinitely — there is no 12-month limit Microsoft's native versioning
      • A version is captured on every import into Blueprint. Because Blueprint does not mirror every version saved in PAD, users can use this to track more intentional, meaningful milestones rather than every incremental save
      • Works with Solution File imports
      • Does not require a Microsoft 365 Auth Setting
    • Microsoft Versioning:
      • Microsoft Versioning mirrors the version history as it exists in Power Automate Desktop.
      • Requires a valid Microsoft 365 Auth Setting to be configured in Blueprint.
      • Versions will only be stored for 12 months.
      • Every time a Flow is saved, a new version is created.
      • Microsoft versioning is enabled by default in all Power Automate environments and cannot be disabled
      • If a Microsoft 365 Auth Setting is removed or deleted after Microsoft Versioning is enabled, Blueprint will automatically revert to Blueprint Versioning.
Also requires MSFT 365 Authentication to be configured (see PAD Export – Link Microsoft 365)

How did we do?

Migrate

Automation360 Authentication Settings

Contact