Skip to content

RecordedFutureIdentity: fix invalid playbook#14197

Merged
v-atulyadav merged 1 commit into
Azure:masterfrom
recordedfuture:fix-rfi-template-bug
May 7, 2026
Merged

RecordedFutureIdentity: fix invalid playbook#14197
v-atulyadav merged 1 commit into
Azure:masterfrom
recordedfuture:fix-rfi-template-bug

Conversation

@aommm
Copy link
Copy Markdown
Contributor

@aommm aommm commented May 4, 2026

Change(s):

  • remove stale references in RFI-confirm-EntraID-risky-user ARM template

Reason for Change(s):

  • The action Check_if_AD_Identity_Protection_risky_users_list_contains_the_user was deleted in v1.2 but its @body() references were left in both response actions, causing InvalidTemplate validation failure at deploy time.

Version Updated:

  • This playbook is NOT part of the main solution, it is only installable from Github. Therefore we have not re-packaged mainTemplate.json or bumped the solution version.

Testing Completed:

  • See guidance below

Checked that the validations are passing and have addressed any issues that are present:

  • See guidance below

… ARM template

The action 'Check_if_AD_Identity_Protection_risky_users_list_contains_the_user'
was deleted in v1.2 but its @Body() references were left in both response actions,
causing InvalidTemplate validation failure at deploy time.

Removes the stale field and schema entry from:
- Response_-_Failed_to_confirm_user_at_risk_is_compromised
- Response_-_Successfully_confirmed_user_at_risk_is_indeed_compromised

Bumps template version to 1.2.1. Fixes RFPD-107446.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@aommm aommm requested review from a team as code owners May 4, 2026 11:04
@v-maheshbh v-maheshbh added the Playbook Playbook specialty review needed label May 5, 2026
@v-shukore
Copy link
Copy Markdown
Contributor

Hi @aommm, please repackage this solution using V3 tool. Thanks!

@aommm
Copy link
Copy Markdown
Contributor Author

aommm commented May 5, 2026

As mentioned in description, I don't think it needs to be packaged. Do you agree @v-shukore?

@v-shukore
Copy link
Copy Markdown
Contributor

Hi @aommm, since you updated the playbook and this is solution content without packaging, your latest changes won’t be reflected in the main template. You’ll need to repackage the solution. Thanks!

@aommm
Copy link
Copy Markdown
Contributor Author

aommm commented May 7, 2026

@v-shukore I don't think that this playbook is solution content. It is not referenced from the Solution.json (or whatever it's called). I did run the packaging script but it only gave me version bumps and TZ changes, nothing relevant.

@v-atulyadav v-atulyadav merged commit 5ed3277 into Azure:master May 7, 2026
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Playbook Playbook specialty review needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants