From 382ef2ee4d25b37480540259d20fe10f297b0615 Mon Sep 17 00:00:00 2001
From: hackerman <3372410+aeneasr@users.noreply.github.com>
Date: Tue, 3 Dec 2024 10:02:35 +0100
Subject: [PATCH] docs: support for oid microsoft parameter (#1936)

---
 docs/kratos/social-signin/20_microsoft.mdx | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/docs/kratos/social-signin/20_microsoft.mdx b/docs/kratos/social-signin/20_microsoft.mdx
index 634471904..4d1d6e250 100644
--- a/docs/kratos/social-signin/20_microsoft.mdx
+++ b/docs/kratos/social-signin/20_microsoft.mdx
@@ -222,9 +222,13 @@ By default, Microsoft uses the identifier taken from the `sub` field of OIDC `id
 the standard OIDC `/userinfo` endpoint.
 
 However, some systems use the `id` field returned by the `https://graph.microsoft.com/v1.0/me` endpoint as a subject identifier.
-To make migrating such systems to the Ory easier, you can use the identifier obtained from the `me` endpoint.
+Others use the `oid` (Object ID) to identify users across different services.
 
-To do that, add the `subject_source` field set to `me` to the social sign-in provider config. Use Ory CLI:
+To make migrating such systems to Ory easier, you can use the identifier obtained from the `me` endpoint and the `oid` field.
+
+### Example
+
+Add the `subject_source` field set to `me` to the social sign-in provider config. Use the Ory CLI:
 
 1. Download the Ory Identities config from your project and save it to a file:
 
@@ -246,7 +250,7 @@ To do that, add the `subject_source` field set to `me` to the social sign-in pro
   - id: microsoft
     (...)
     // highlight-start
-    subject_source: me
+    subject_source: me # or oid
     # or
     # subject_source: userinfo
     scope: