Merge pull request #249367 from csmulligan/csmulligan-patch-1

[B2B] "phone" identity clarification (ADO-149126)

Author: prmerger-automator[bot]

articles/active-directory/external-identities/user-properties.md

@@ -79,7 +79,7 @@ This property indicates the relationship of the user to the host tenancy. This p
 This property indicates the user’s primary identity provider. A user can have several identity providers, which can be viewed by selecting the link next to **Identities** in the user’s profile or by querying the `identities` property via the Microsoft Graph API.
 
 > [!NOTE]
-> Identities and UserType are independent properties. A value of Identities does not imply a particular value for UserType
+> Identities and UserType are independent properties. A value of Identities does not imply a particular value for UserType.
 
 Identities property value | Sign-in state
 --------------------- | -------------------------
@@ -91,6 +91,8 @@ facebook.com | This user has a Facebook account and has signed up by using self-
 mail | This user has signed up by using Azure AD Email one-time passcode (OTP).
 {issuer URI} | This user is homed in an external organization that doesn't use Azure Active Directory as their identity provider, but instead uses a SAML/WS-Fed-based identity provider. The issuer URI is shown when the Identities field is clicked.
 
+Phone sign-in is not supported for external users. B2B accounts cannot use `phone`value as an identity provider. 
+
 ### Directory synced
 
 The **Directory synced** property indicates whether the user is being synced with on-premises Active Directory and is authenticated on-premises. This property is **Yes** if the account is homed in the organization’s on-premises Active Directory and synced with Azure AD, or **No** if the account is a cloud-only Azure AD account. In Microsoft Graph, the Directory synced property corresponds to `onPremisesSyncEnabled`.