resolve GitHub issue 84895

Author: kengaderdus

articles/active-directory-b2c/saml-identity-provider-technical-profile.md

@@ -179,38 +179,6 @@ The **CryptographicKeys** element contains the following attributes:
 | SamlAssertionDecryption |No | The X509 certificate (RSA key set). A SAML identity provider uses the public portion of the certificate to encrypt the assertion of the SAML response. Azure AD B2C uses the private portion of the certificate to decrypt the assertion. |
 | MetadataSigning |No | The X509 certificate (RSA key set) to use to sign SAML metadata. Azure AD B2C uses this key to sign the metadata.  |
 
-## SAML entityID customization
-
-If you have multiple SAML applications that depend on different entityID values, you can override the `issueruri` value in your relying party file. To do this, copy the technical profile with the "Saml2AssertionIssuer" ID from the base file and override the `issueruri` value.
-
-> [!TIP]
-> Copy the `<ClaimsProviders>` section from the base and preserve these elements within the claims provider: `<DisplayName>Token Issuer</DisplayName>`, `<TechnicalProfile Id="Saml2AssertionIssuer">`, and `<DisplayName>Token Issuer</DisplayName>`.
- 
-Example:
-
-```xml
-   <ClaimsProviders>   
-    <ClaimsProvider>
-      <DisplayName>Token Issuer</DisplayName>
-      <TechnicalProfiles>
-        <TechnicalProfile Id="Saml2AssertionIssuer">
-          <DisplayName>Token Issuer</DisplayName>
-          <Metadata>
-            <Item Key="IssuerUri">customURI</Item>
-          </Metadata>
-        </TechnicalProfile>
-      </TechnicalProfiles>
-    </ClaimsProvider>
-  </ClaimsProviders>
-  <RelyingParty>
-    <DefaultUserJourney ReferenceId="SignUpInSAML" />
-    <TechnicalProfile Id="PolicyProfile">
-      <DisplayName>PolicyProfile</DisplayName>
-      <Protocol Name="SAML2" />
-      <Metadata>
-     …
-```
-
 ## Next steps
 
 See the following articles for examples of working with SAML identity providers in Azure AD B2C: