Migrate native authentication with the AI agent toolkit
In brief
The new how-to describes using the `eeid-native-auth-migrate-v2` skill to plan, approve, apply, security-review, and validate migrations for supported app integrations.
What Entra admins need to know
Administrators and app teams can use a reviewable, scoped migration process and keep changes in the working tree for review before committing.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
new file mode 100644
title: Migrate native authentication with the AI agent toolkit description: Use the eeid-native-auth-migrate-v2 skill to plan, approve, apply, and validate a native authentication V1-to-V2 migration in your app. ms.topic: how-to ms.date: 11/11/2026 ai-usage: ai-generated ms.custom: msecd-doc-authoring-1030 # Customer intent: As an app developer, I want to migrate selected native authentication flows from V1 to V2 with an AI coding agent so that I can review the scope, approve changes, and validate the result.
Migrate native authentication from V1 to V2 with the AI agent toolkit
Use the eeid-native-auth-migrate-v2 skill to migrate an existing app's native authentication from V1 to V2. The skill inventories your code, creates a reviewable plan, applies approved changes, reviews those changes for security, and reports validation results.
You can migrate sign-in, sign-up, and self-service password reset together or one flow at a time. Multifactor authentication and strong authentication method registration move with the flow they belong to.
[!INCLUDE applies-to-external-only]
Prerequisites
- Completion of Install the AI agent toolkit.
- An existing app that uses native authentication V1, with source code the agent can inspect and change.
Build and unit test tools are recommended for validation, but they aren't required to use the skill. If you choose to run validation commands, make sure your project's tools are available.
Use the skill with one of these integration approaches:
- An app that calls the native authentication API directly.
- A JavaScript single-page app that uses MSAL native authentication.
- An Android app that uses MSAL native authentication.
- An iOS or macOS app that uses MSAL native authentication.
The direct API approach isn't limited to the SDK platforms listed here. The skill needs access to the app-owned HTTP calls and flow code. It isn't a guide for adding authentication to a new app, upgrading an MSAL package on its own, or changing browser-redirect authentication.
Start the migration and choose its scope
Start in the app you want to migrate. The skill inspects V1 usage before proposing code changes.
Open your app's source folder in your coding agent. If the workspace contains several apps, identify the app to migrate.
Ask the agent to use
eeid-native-auth-migrate-v2. Choose the request that matches your intended scope:- To migrate all flows, enter
Migrate my app's native auth from V1 to V2. - To migrate sign-in only, enter
Migrate only sign-in to native auth V2 and keep the other flows on V1.
- To migrate all flows, enter
Review the agent's inventory and any questions about the integration approach or scope.
If the skill doesn't start, name it explicitly in your request. In coding agents that support it, you can enter /eeid-native-auth-migrate-v2.
The skill writes .native-auth-v2-migration/plan.md in your app's root folder. It doesn't change application code before you approve the plan.
Review and revise the migration plan
The plan records what changes, what stays on V1, what users will notice, and how the migration is validated.
- Open
.native-auth-v2-migration/plan.md. - Confirm the selected flows and deferred flows. Check that changes to shared code preserve the flows that remain on V1.
- Review the proposed behavior changes, implementation tasks, and open decisions.
- Review any planned validation commands and their baseline and post-change runs. Adjust the plan's validation settings with the agent if needed.
- Answer open decisions and request revisions until the scope is correct. For example, enter
Remove password reset from the migration plan.
Different flows can use different versions, but a single flow can't mix V1 and V2. This boundary includes MFA and method registration that occur within the flow.
Each plan change needs approval of the new revision. Resolve open decisions before approving.
Approve and apply the plan
Approval authorizes the current plan revision, including its validation commands. Review the plan before giving that approval.
Confirm that the plan matches your intended scope and has no unresolved decisions.
Approve the plan in chat. For example, enter:
The plan looks good. Approved, go ahead.Let the agent perform its pre-apply check and any planned baseline validation. If files changed since planning or an in-scope file has uncommitted changes, resolve the conflict and review any revised plan before continuing.
Let the agent apply the approved changes, update the applicable tests, review its changes for security, and run any planned validation commands.
The eeid-native-auth-migrate-v2 workflow doesn't commit, push, or create branches. It leaves changes in your working tree for you to review.
Check the report and test the app
The migration report records the outcome rather than assuming every check passed.
- Open
.native-auth-v2-migration/report.md. - Review the outcome, deviations from the plan, security review findings, and baseline and post-change validation results. Check the reasons for any failed or not-run checks.
- Review the application changes in your working tree.
- Perform the manual tests listed in the report for the migrated flows and any deferred flows that share code.
Keep unresolved findings and manual tests visible when deciding whether the migration is ready for your own commit and release.
Continue a migration or migrate deferred flows
The migration folder records progress so that the skill can determine the next step.
- To resume an interrupted migration, ask the agent to use the skill and enter
Continue my native auth migration. - After a phase is reported, review the outcome before starting deferred flows. To continue with the remaining flows, enter
Start the next phase and migrate the remaining flows to V2.
An unfinished plan created by a different version of the skill can't be continued as-is. The skill requires its version-change restart procedure instead.
Related content
- Explore the AI agent toolkit overview and available skills.
- Learn how to onboard an app with the toolkit.
- Review the native authentication overview.
@@ -0,0 +1,105 @@+---+title: Migrate native authentication with the AI agent toolkit+description: Use the eeid-native-auth-migrate-v2 skill to plan, approve, apply, and validate a native authentication V1-to-V2 migration in your app.+ms.topic: how-to+ms.date: 11/11/2026+ai-usage: ai-generated+ms.custom: msecd-doc-authoring-1030+# Customer intent: As an app developer, I want to migrate selected native authentication flows from V1 to V2 with an AI coding agent so that I can review the scope, approve changes, and validate the result.+---++# Migrate native authentication from V1 to V2 with the AI agent toolkit++Use the `eeid-native-auth-migrate-v2` skill to migrate an existing app's native authentication from V1 to V2. The skill inventories your code, creates a reviewable plan, applies approved changes, reviews those changes for security, and reports validation results.++You can migrate sign-in, sign-up, and self-service password reset together or one flow at a time. Multifactor authentication and strong authentication method registration move with the flow they belong to.++[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]++## Prerequisites++- Completion of [Install the AI agent toolkit](how-to-install-ai-agent-toolkit.md).+- An existing app that uses native authentication V1, with source code the agent can inspect and change.++Build and unit test tools are recommended for validation, but they aren't required to use the skill. If you choose to run validation commands, make sure your project's tools are available.++Use the skill with one of these integration approaches:++- An app that calls the native authentication API directly.+- A JavaScript single-page app that uses MSAL native authentication.+- An Android app that uses MSAL native authentication.+- An iOS or macOS app that uses MSAL native authentication.++The direct API approach isn't limited to the SDK platforms listed here. The skill needs access to the app-owned HTTP calls and flow code. It isn't a guide for adding authentication to a new app, upgrading an MSAL package on its own, or changing browser-redirect authentication.++## Start the migration and choose its scope++Start in the app you want to migrate. The skill inspects V1 usage before proposing code changes.++1. Open your app's source folder in your coding agent. If the workspace contains several apps, identify the app to migrate.+1. Ask the agent to use `eeid-native-auth-migrate-v2`. Choose the request that matches your intended scope:++ - To migrate all flows, enter `Migrate my app's native auth from V1 to V2`.+ - To migrate sign-in only, enter `Migrate only sign-in to native auth V2 and keep the other flows on V1`.++1. Review the agent's inventory and any questions about the integration approach or scope.++If the skill doesn't start, name it explicitly in your request. In coding agents that support it, you can enter `/eeid-native-auth-migrate-v2`.++The skill writes `.native-auth-v2-migration/plan.md` in your app's root folder. It doesn't change application code before you approve the plan.++## Review and revise the migration plan++The plan records what changes, what stays on V1, what users will notice, and how the migration is validated.++1. Open `.native-auth-v2-migration/plan.md`.+1. Confirm the selected flows and deferred flows. Check that changes to shared code preserve the flows that remain on V1.+1. Review the proposed behavior changes, implementation tasks, and open decisions.+1. Review any planned validation commands and their baseline and post-change runs. Adjust the plan's validation settings with the agent if needed.+1. Answer open decisions and request revisions until the scope is correct. For example, enter `Remove password reset from the migration plan`.++Different flows can use different versions, but a single flow can't mix V1 and V2. This boundary includes MFA and method registration that occur within the flow.++Each plan change needs approval of the new revision. Resolve open decisions before approving.++## Approve and apply the plan++Approval authorizes the current plan revision, including its validation commands. Review the plan before giving that approval.++1. Confirm that the plan matches your intended scope and has no unresolved decisions.+1. Approve the plan in chat. For example, enter:++ ```text+ The plan looks good. Approved, go ahead.+ ```++1. Let the agent perform its pre-apply check and any planned baseline validation. If files changed since planning or an in-scope file has uncommitted changes, resolve the conflict and review any revised plan before continuing.+1. Let the agent apply the approved changes, update the applicable tests, review its changes for security, and run any planned validation commands.++The `eeid-native-auth-migrate-v2` workflow doesn't commit, push, or create branches. It leaves changes in your working tree for you to review.++## Check the report and test the app++The migration report records the outcome rather than assuming every check passed.++1. Open `.native-auth-v2-migration/report.md`.+1. Review the outcome, deviations from the plan, security review findings, and baseline and post-change validation results. Check the reasons for any failed or not-run checks.+1. Review the application changes in your working tree.+1. Perform the manual tests listed in the report for the migrated flows and any deferred flows that share code.++Keep unresolved findings and manual tests visible when deciding whether the migration is ready for your own commit and release.++## Continue a migration or migrate deferred flows++The migration folder records progress so that the skill can determine the next step.++1. To resume an interrupted migration, ask the agent to use the skill and enter `Continue my native auth migration`.+1. After a phase is reported, review the outcome before starting deferred flows. To continue with the remaining flows, enter `Start the next phase and migrate the remaining flows to V2`.++An unfinished plan created by a different version of the skill can't be continued as-is. The skill requires its version-change restart procedure instead.++## Related content++- Explore the [AI agent toolkit overview and available skills](ai-agent-toolkit-overview.md).+- Learn how to [onboard an app with the toolkit](how-to-ai-agent-toolkit-onboard.md).+- Review the [native authentication overview](~/identity-platform/concept-native-authentication.md). 