Skip to main content

Notifications

Power Automate - General Discussion
Unanswered

Best Practices for Restricting RPA Bot Accounts Usage in Power Automate

(1) ShareShare
ReportReport
Posted on by 117

Hello everyone,

In my RPA team, we use Power Automate and rely on bot accounts (service accounts) as the actual users executing automations on virtual machines. However, I’m facing a challenge: my developers tend to use these bot accounts for development and testing instead of using their own individual accounts.

This practice creates issues with traceability, as it becomes harder to track who is doing what. I would like to ensure that developers use their personal Active Directory (AD) accounts for development while reserving the bot accounts strictly for automation execution.

I’m looking for ideas or strategies to enforce this. Ideally, I’d like to:

  1. Limit developers’ ability to log in and work directly under the bot account.
  2. Possibly restrict the bot account’s access in the Power Platform environment to only what is necessary for automation.

Has anyone dealt with a similar situation before? Any tips, best practices, or technical configurations to achieve this?

Thanks in advance for your help!

Categories:

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,475

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,767

Leaderboard