Power Platform Community Forum Thread Details

@BJ-12111655-0

You're attempting to use Apple as an identity provider in Power Pages integrated with Dynamics, and encountering a situation where no response is formed after sending an invitation via a model-driven app. This issue is likely tied to how identity claims are mapped and how the authentication flow is configured between Apple ID, Power Pages, and Dataverse.

🔍 Key Findings from Internal and External Sources

1. Apple Business Chat and Identity Requirements

The Business-Chat-GettingStarted-Guide outlines strict requirements for Apple-based identity and messaging integrations:

Apple mandates human support availability and explicit disclosure for automated agents.
Message routing must use Intent ID and Group ID, which may not be configured correctly in your current setup.
Apple prohibits unsolicited messages, which could interfere with invitation-based flows.

2. Dataverse Identity Mapping

From the Dynamics community, a similar issue was resolved by:

Ensuring the adx_identity_username field in the Dataverse Contact table is correctly populated with the Apple object ID.
Creating a record in the External Identity table with:
- adx_username = Apple object ID
- adx_identityprovidername = Apple issuer URL
- adx_contactid = matched contact ID
Setting adx_identity_logonenabled = true and generating a adx_identity_securitystamp if missing.

This mapping ensures that Power Pages can recognize the identity returned by Apple and link it to a valid contact.

3. Invitation Flow Conflicts

If you're using a model-driven app to send invitations, and registration is disabled in Power Pages, the identity provider may not be able to complete the handshake. You should:

Confirm that registration is disabled in Power Pages Identity Provider settings.
Ensure the Apple ID token includes all required claims (e.g., email, name, sub) and that your Azure AD B2C or custom policy can parse them.

✅ Recommended Steps to Resolve

Verify Identity Provider Configuration
- Ensure the issuer URL for Apple is correctly set in Power Pages.
- Confirm that the authority URL is not mistakenly used as the identity provider name.
Check Dataverse Contact Mapping
- Use a backend function (e.g., Azure Function App) to search for the Apple object ID in adx_identity_username.
- If not found, match by name/email and create the mapping manually.
Enable Logging and Claims Inspection
- Use browser dev tools or Azure AD B2C logs to inspect the token returned by Apple.
- Confirm that the token includes all required claims and that Power Pages is configured to accept them.
Test Without Invitation Flow
- Try a direct login flow without using the model-driven app invitation to isolate the issue.

🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.