Forum Discussion
Service Principal for Semantic model Refresh Issue
- 6 months ago
You would have to enter the Application (Client) ID of the Azure AD app registration you created (not the object ID).
This is exactly what “Service principal ID” refers to in the UI.So you should have:
- Tenant ID = Directory ID from Azure AD
- Service Principal ID = Application (Client) ID
- Service Principal Key = the client secret under Certificates & secrets
Your tenant admin who has created the service pricipal SPN for you should have shared the client secret already.
Hope this helps - please appreciate by leaving a Kudos or accepting as a Solution!
Hi JibinSebastian ,
Please find the steps to Fix the issue
Recreate the connection:
Go to the workspace → Create new connection
Use:
Tenant ID = Directory ID
Service Principal ID = Application (Client) ID
Service Principal Key = Client secret value
Verify permissions:
The SP must be assigned to the workspace (Contributor or Member role)
Ensure the SP is allowed under tenant settings:
Admin portal → Tenant settings → Service principals
Use the SP to bind the semantic model:
When using the SP for scheduled refresh, make sure it’s added as a Gateway Connection credential (if applicable).
If everything is configured correctly and the token issue persists, you might also want to:
Generate a new client secret
Clear and reconfigure the connection using updated credentials
If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!