[Append](#append) [AppRoleAssignmentsComplex](#approleassignmentscomplex) [BitAnd](#bitand) [CBool](#cbool) [CDate](#cdate) [Coalesce](#coalesce) [ConvertToBase64](#converttobase64) [ConvertToUTF8Hex](#converttoutf8hex) [Count](#count) [CStr](#cstr) [DateAdd](#dateadd) [DateDiff](#datediff) [DateFromNum](#datefromnum) [DefaultDomain](#defaultdomain) [FormatDateTime](#formatdatetime) [Guid](#guid) [IgnoreFlowIfNullOrEmpty](#ignoreflowifnullorempty) [IIF](#iif) [InStr](#instr) [IsNull](#isnull) [IsNullOrEmpty](#isnullorempty) [IsPresent](#ispresent) [IsString](#isstring) [Item](#item) [Join](#join) [Left](#left) [Len](#len) [Mid](#mid) [NormalizeDiacritics](#normalizediacritics) [Not](#not) [Now](#now) [NumFromDate](#numfromdate) [PCase](#pcase) [RandomString](#randomstring) [Redact](#redact) [RemoveDuplicates](#removeduplicates) [Replace](#replace) [SelectUniqueValue](#selectuniquevalue) [SingleAppRoleAssignment](#singleapproleassignment) [Split](#split) [StripSpaces](#stripspaces) [Switch](#switch) [ToLower](#tolower) [ToUpper](#toupper) [Word](#word)
Global Relay SCIM authorization warning stands out in an otherwise documentation-only Entra ID day
On 14 April 2026, the feed contains 19 updated Microsoft Learn entries for Entra ID, with no new or removed items and no Message Center notices. The meaningful operational signal is a warning that the Global Relay Identity Sync provisioning connector uses a SCIM authorization method that is no longer supported because of security concerns; the other updates are primarily routine provisioning, SCIM reference, and passkey/FIDO2 documentation edits. No new Entra capability, preview, GA, or broad behavior change is evidenced.
- Global Relay Identity Sync SCIM authorization is flagged as unsupported
Entra ID · StandardsThe Entra ID provisioning tutorial says the connector uses a SCIM authorization method that is no longer supported due to security concerns, and that efforts are underway with Global Relay to switch to a more secure authorization method. This is a security and compatibility warning; the update does not state a migration deadline or that the connector has already stopped functioning.
- Passkey guidance was cross-linked to dedicated FIDO2 support documentation
Entra ID · AuthenticationThe passkey authentication page now directs readers to the Microsoft Entra FIDO2 support article. This is an ordinary documentation-navigation clarification, not evidence of a new passkey feature, preview, or general availability change.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
19 updates
Microsoft Entra ID
19 updatesFoodee Provisioning Tutorial
Updated1. Under **Enterprise portal**, select **Single Sign On**.
1. In the **Tenant URL** field, input your Cisco User Management for Secure Access Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cisco User Management for Secure Access. If the connection fails, ensure your Cisco User Management for Secure Access account has the required admin permissions and try again.
1. Under **Mappings**, select the object (user or group) for which you'd like to add a custom attribute.
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
Figma Provisioning Tutorial
Updated1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
Flock Provisioning Tutorial
Updated1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
Gong Provisioning Tutorial
Updated1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
Chaos Provisioning Tutorial
Updated1. In the **Tenant URL** field, input your Chaos Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chaos. If the connection fails, ensure your Chaos account has the required admin permissions and try again.
1. In the **Tenant URL** field, input your Chatwork Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Chatwork. If the connection fails, ensure your Chatwork account has the required admin permissions and try again.
1. In the **Tenant URL** field, input your CheckProof Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to CheckProof. If the connection fails, ensure your CheckProof account has the required admin permissions and try again.
Cinode Provisioning Tutorial
Updated1. In the **Tenant URL** field, input your Cinode Tenant URL and Secret Token. Select **Test Connection** to ensure Microsoft Entra ID can connect to Cinode. If the connection fails, ensure your Cinode account has the required admin permissions and try again.
> Global Relay Identity Sync provisioning connector utilizes a SCIM authorization method that's no longer supported due to security concerns. Efforts are underway with Global Relay to switch to a more secure authorization method.
Fido2 Compatibility
UpdatedFor more information about how to sign in with FIDO2 security keys on a Windows device, see [Enable FIDO2 security key sign-in to Windows 10 and 11 devices with Microsoft Entra ID](howto-authentication-passwordless-security-key-windows.md).
For more information about passkey authentication, see [Support for FIDO2 authentication with Microsoft Entra ID](~/identity/authentication/concept-fido2-compatibility.md).
Wrike Provisioning Tutorial
UpdatedMicrosoft Entra ID uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users or groups that were assigned to an application in Microsoft Entra ID are synchronized.