How do I install the Orchardcore Microsoft Auth skill?

Run npx skillmds@latest add crestapps/orchardcore-microsoft-auth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orchardcore Microsoft Auth safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orchardcore Microsoft Auth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orchardcore Microsoft Auth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Orchardcore Microsoft Auth?

CrestApps (@crestapps) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orchardcore Microsoft Auth by crestapps

Name: Orchardcore Microsoft Auth
Rating: 4.2 (5 reviews)
Author: CrestApps

Orchardcore Microsoft Auth

Skill for configuring Microsoft authentication in Orchard Core. Covers Microsoft Account login, Microsoft Entra ID authentication, current feature IDs, current settings paths, MicrosoftAccountSettings and AzureADSettings recipes, and callback URL setup. Use this skill when requests mention Orchard Core Microsoft Authentication, Microsoft Account Authentication, Microsoft Account Settings, Microsoft Entra ID Authentication, Entra ID Settings, or closely related Orchard Core implementation, setup, extension, or troubleshooting work.

CrestApps Updated Sep 10, 2026

File contents

Orchard Core Microsoft Authentication

Enable one or both external-authentication features:

Feature ID	Settings path
`OrchardCore.Microsoft.Authentication.MicrosoftAccount`	Settings → Security → Authentication → Microsoft
`OrchardCore.Microsoft.Authentication.AzureAD`	Settings → Security → Authentication → Microsoft Entra ID

Both depend on OrchardCore.Users.ExternalAuthentication. Register each tenant's exact HTTPS callback URL at the provider.

Microsoft Account

The default callback path is /signin-microsoft. The module's recipe handler is named MicrosoftAccountSettings:

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.Microsoft.Authentication.MicrosoftAccount"
      ]
    },
    {
      "name": "MicrosoftAccountSettings",
      "AppId": "microsoft-application-id",
      "AppSecret": "supply-from-a-secret-store",
      "CallbackPath": "/signin-microsoft"
    }
  ]
}

Microsoft Entra ID

The Entra recipe handler is AzureADSettings:

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.Microsoft.Authentication.AzureAD"
      ]
    },
    {
      "name": "AzureADSettings",
      "DisplayName": "Sign in with Microsoft Entra ID",
      "AppId": "entra-application-id",
      "TenantId": "organizations",
      "CallbackPath": "/signin-oidc"
    }
  ]
}

Use the specific configuration extension for environment-backed secrets and enable OrchardCore.Users.Registration only when external identities may create local Orchard users.

---name: orchardcore-microsoft-authdescription: Skill for configuring Microsoft authentication in Orchard Core. Covers Microsoft Account login, Microsoft Entra ID authentication, current feature IDs, current settings paths, MicrosoftAccountSettings and AzureADSettings recipes, and callback URL setup. Use this skill when requests mention Orchard Core Microsoft Authentication, Microsoft Account Authentication, Microsoft Account Settings, Microsoft Entra ID Authentication, Entra ID Settings, or closely related Orchard Core implementation, setup, extension, or troubleshooting work.---# Orchard Core Microsoft AuthenticationEnable one or both external-authentication features:| Feature ID | Settings path ||---|---|| `OrchardCore.Microsoft.Authentication.MicrosoftAccount` | **Settings → Security → Authentication → Microsoft** || `OrchardCore.Microsoft.Authentication.AzureAD` | **Settings → Security → Authentication → Microsoft Entra ID** |Both depend on `OrchardCore.Users.ExternalAuthentication`. Register eachtenant's exact HTTPS callback URL at the provider.## Microsoft AccountThe default callback path is `/signin-microsoft`. The module's recipe handleris named `MicrosoftAccountSettings`:```json{ "steps": [ { "name": "Feature", "enable": [ "OrchardCore.Microsoft.Authentication.MicrosoftAccount" ] }, { "name": "MicrosoftAccountSettings", "AppId": "microsoft-application-id", "AppSecret": "supply-from-a-secret-store", "CallbackPath": "/signin-microsoft" } ]}```## Microsoft Entra IDThe Entra recipe handler is `AzureADSettings`:```json{ "steps": [ { "name": "Feature", "enable": [ "OrchardCore.Microsoft.Authentication.AzureAD" ] }, { "name": "AzureADSettings", "DisplayName": "Sign in with Microsoft Entra ID", "AppId": "entra-application-id", "TenantId": "organizations", "CallbackPath": "/signin-oidc" } ]}```Use the specific configuration extension for environment-backed secrets andenable `OrchardCore.Users.Registration` only when external identities maycreate local Orchard users.

Frequently asked questions