Teams Integration Settings save failure for custom table RFQ in PROD managed environment

(1) Share

Report

Posted on by omkarsupreme

Unable to add custom table RFQ as a Record Type in Teams Integration Settings in Power Platform Admin Center in PROD environment.

Same configuration works in DEV and UAT environments.

Categories:

Building Power Apps

Connector development

Experimental features

Microsoft Dataverse with Power Apps

Error handling

Power Apps Pro Dev & ISV

Power Query

General topics

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Valantis 6,341 on at

Like (1)

Report
Copy link

Link copied!

Hi @omkarsupreme,

The fact that it works in DEV and UAT but fails in PROD points to the managed environment or solution layer differences.
Things to check:

1. Is the RFQ table properly deployed to PROD as part of a managed solution? If the table exists in PROD but has a different schema version or is missing components that DEV/UAT have, Teams Integration Settings may refuse to add it.

2. Check if the RFQ table has the "Enable for Teams integration" option enabled in the table settings. In PROD with managed solutions, this property may be locked if the managing solution doesn't include it. The property to check: Table > Properties > Enable for Teams Integration.

3. If PROD is a Managed Environment, check whether there's a policy or governance setting that restricts Teams integration to specific tables only.
4. Compare the exact error message when saving fails. Is it a permissions error, a validation error, or a silent failure? The error text usually points directly at the cause.

5. Check if your user has System Administrator role in PROD. Teams Integration Settings requires higher privileges than Environment Maker.
What exact error do you see when trying to save?

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
omkarsupreme 83 on at

Like (0)

Report
Copy link

Link copied!

Hi @Valantis

unable the change the below settings also

Was this reply helpful? Yes No
Suggested answer

Valantis 6,341 on at

Like (1)

Report
Copy link

Link copied!

Hi @omkarsupreme,

That confirms it, the "Enable for Teams Integration" setting is locked because the RFQ table in PROD is managed and the managing solution doesn't include that property as customizable.

try this:

1. In your DEV environment, open the solution that contains the RFQ table
2. Find the RFQ table > Properties > make sure "Enable for Teams Integration" is checked and save
3. Export the solution from DEV as managed
4. Import/deploy it to PROD

The setting needs to be set in the source solution in DEV and deployed through your normal ALM process. You can't change it directly in PROD when it's locked by a managed layer.

If the solution is already deployed to PROD managed and you can't redeploy right now, the workaround is to create a small unmanaged solution in PROD, add the RFQ table as a component, and then enable the Teams Integration property there.

This creates an unmanaged layer on top of the managed one that unlocks the setting. Note: this should then be merged back into your managed solution properly.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
omkarsupreme 83 on at

Like (0)

Report
Copy link

Link copied!
Hi @Valantis,

One thing I'm trying to understand is why the same approach worked in UAT but not in PROD.

Both environments have the same managed solution deployed, and I was able to enable the setting in UAT using the workaround.

Could you advise what differences I should check between UAT and PROD? For example:

Solution layers on the RFQ table - no any unmanaged layer present

Presence of any unmanaged customizations

Managed solution version or patches

Environment-level Teams integration settings

Is there a specific reason why the workaround would be successful in UAT but not in PROD despite having the same managed solution?

Thanks.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,341 on at

Like (1)

Report
Copy link

Link copied!

Hi @omkarsupreme,

If same managed solution, same version, same workaround approach the most likely explanation is a Managed Environment policy difference between UAT and PROD.

Things to compare specifically:
1. Managed Environment settings: go to PPAC > Environments > select each environment > Managed Environments. Check if PROD has stricter settings than UAT, particularly any solution checker or customization policies that block unmanaged layers.

2. System Administrator role: even if you have the same role in both environments, verify that your account is explicitly listed as System Administrator in PROD (not just inherited through a team). Some PROD environments have stricter admin controls.

3. Environment security group: if PROD has an Entra security group restricting access, your account might have slightly different effective permissions than in UAT even with the same role.

4. Check the PROD solution layers: in PPAC > Solutions > select the solution > find the RFQ table > Solution Layers. If there's an existing unmanaged layer in UAT that was created before (leftover from testing) and PROD never had one, that explains why UAT accepted the workaround and PROD doesn't.

5. Try creating the unmanaged solution workaround in PROD again but this time via a System Administrator account that is directly assigned (not group-inherited). If the error is different it will point at the exact blocker.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No