Merge pull request #189258 from amanmcse/patch-35

(AzureCXP) fixes MicrosoftDocs/azure-docs#88383

Author: PRMerger16

articles/active-directory-b2c/saml-service-provider-options.md

@@ -291,18 +291,20 @@ For example, when `TokenNotBeforeSkewInSeconds` is set to `120` seconds:
 You can specify whether milliseconds will be removed from date and time values within the SAML response. (These values include `IssueInstant`, `NotBefore`, `NotOnOrAfter`, and `AuthnInstant`.) To remove the milliseconds, set the `RemoveMillisecondsFromDateTime` metadata key within the relying party. Possible values: `false` (default) or `true`.
 
 ```xml
-<ClaimsProvider>
-  <DisplayName>Token Issuer</DisplayName>
-  <TechnicalProfiles>
-    <TechnicalProfile Id="Saml2AssertionIssuer">
-      <DisplayName>Token Issuer</DisplayName>
-      <Protocol Name="SAML2"/>
-      <OutputTokenFormat>SAML2</OutputTokenFormat>
+  <RelyingParty>
+    <DefaultUserJourney ReferenceId="SignUpOrSignIn" />
+    <TechnicalProfile Id="PolicyProfile">
+      <DisplayName>PolicyProfile</DisplayName>
+      <Protocol Name="SAML2" />
       <Metadata>
         <Item Key="RemoveMillisecondsFromDateTime">true</Item>
       </Metadata>
-      ...
+      <OutputClaims>
+             ...
+      </OutputClaims>
+      <SubjectNamingInfo ClaimType="objectId" ExcludeAsClaim="true" />
     </TechnicalProfile>
+  </RelyingParty>
 ```
 
 ## Use an issuer ID to override an issuer URI
@@ -395,4 +397,4 @@ By using these tools, you can check the integration between your application and
 <!-- LINKS - External -->
 [samltest]: https://aka.ms/samltestapp
 
-::: zone-end
+::: zone-end