Microsoft Fabric: Changes to delegation capabilities for Microsoft Azure OpenAI tenant settings [MC1062450]

Microsoft Fabric: Changes to delegation capabilities for Microsoft Azure OpenAI tenant settings [MC1062450]

Message ID: MC1062450

Coming soon: An update to the behavior of an existing tenant setting in Microsoft Fabric that allows Fabric admins to enable Microsoft Copilot and other features powered by Microsoft Azure OpenAI in Fabric.

  • Fabric tenant setting name: Users can use Copilot and other features powered by Azure OpenAI
  • Impact: No impact if no action is taken

This feature does not require an additional Microsoft 365 Copilot license. Only Fabric capacity is required.

[When this will happen:]

Starting May 12, 2025, this change will be incrementally rolled out to all customers of Fabric.

Fabric service admins can check the visual cue at the top of the Tenant settings page to check when the setting behavior has been updated and take action as necessary.

[How this will affect your organization:]

What is the change?

Before this rollout, this setting is delegated to capacity admins by default and cannot be changed by tenant admins. That is, tenant admins cannot take back control of this setting from their capacity admins and drive feature management at the tenant level.

After this rollout, tenant admins will be able to take back control of this setting from their capacity admins. Tenant admins can remove delegation if necessary by unchecking Capacity admins can enable/disable in the Fabric Admin portal at Tenant settings > Users can use Copilot and other features powered by Azure OpenAI.

Tenant settings delegation to capacity admins in Fabric:

admin controls

[What you need to do to prepare:]

If you do not intend to remove delegation for this setting, no action is needed for your tenant. The current setting value and the corresponding capacity level values do not change when this new behavior is rolled out.

If you do intend on taking back control of this setting from the capacity admins, follow these steps:

  • Review and decide the appropriate settings for your tenant. Review the implications of taking back control:
    • Capacity admins will no longer be able to see this setting in the Delegated tenant settings tab in the Capacity settings.
    • If delegation is disabled, all capacities will follow the tenant setting values and cannot override tenant admin selection.
    • If setting is enabled for the capacity and delegation is removed with tenant-level value as Off, then existing Copilot features will stop for users in the capacity. Consider communicating to capacity admins before removing delegation.
    • Watch a short video (no sound, 00:19 seconds)
  • Action for Microsoft 365 global admins and Fabric admins: If no action is taken, the current behavior for this setting across the tenant and capacity level does not change. If you opt to remove delegation, we recommend communicating to your capacity admins and implications.

We encourage you to assess the behavior update and make any necessary changes to align with your organization’s compliance policies. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.

If you have any questions or need further assistance, please do not hesitate to contact our support team.

Learn more: Overview of Copilot in Fabric – Microsoft Fabric | Microsoft Learn

Source: Microsoft

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The recent update to Microsoft Fabric regarding delegation capabilities for Microsoft Azure OpenAI tenant settings is set to create quite a stir, and for good reason! This change will allow tenant admins to regain control over the setting that enables Microsoft Copilot and other features powered by Azure OpenAI, a shift that could have significant implications for both admins and users.

    For admins, this update means empowerment. Previously, capacity admins held the reins regarding the use of Copilot features, and tenant admins had to sit on the sidelines. Now, tenant admins can take back control, ensuring that feature management aligns with organizational policies. This newfound authority can streamline decision-making and enhance compliance, which is a win-win for everyone involved!

    On the user side, the impact is a bit more nuanced. If tenant admins choose to remove the delegation, users in those capacities may find themselves abruptly cut off from Copilot features. This could lead to some confusion if not communicated effectively. Therefore, it’s essential for tenant admins to keep the lines of communication open and ensure their users are aware of any changes that may affect their day-to-day operations.

    The overall impact of these changes could be quite substantial, depending on how organizations choose to implement them. For some, it may mean a more cohesive approach to feature management, while for others, it could lead to temporary disruptions if delegation is removed without proper notice.

    In conclusion, while the update doesn’t require immediate action if no changes are desired, it certainly opens the door for a more controlled and compliant environment. So, admins, take a moment to assess your current settings—do you want to hold the reins, or are you comfortable letting capacity admins steer the ship?

    And readers, I’d love to hear your thoughts! How do you think this update will impact your organization? Share your insights in the comments below, and let’s spark a conversation! For more on this topic, check out additional posts at mwpro.co.uk.

Leave a Reply

Your email address will not be published. Required fields are marked *