[BUG] fab config set workspace_private_links_enabled true returns InvalidInput although listed as available setting

[mkufa]

Bug Description

When attempting to enable the configuration setting workspace_private_links_enabled via the fab CLI, the command fails with an InvalidInput error, despite the setting appearing to be available.

Impact
Blocks enabling Private Link-related configuration via CLI, which is critical for secure enterprise deployments (e.g. environments requiring network isolation and compliance controls).

fabric-cli version

1.6.1

Python version

3.13

Operating System

Windows

CLI Mode

Interactive mode

Authentication Method

Interactive browser login

Steps to Reproduce

1. Run the following command:
   fab config set workspace_private_links_enabled true
2. Observe the error message:
   x config set: [InvalidInput] 'workspace_private_links_enabled' is not a known configuration key
3. List available configuration settings:
   fab config ls
4. Review output (excerpt):

---------------------------------------------
cache_enabled                 true
debug_enabled                 false
encryption_fallback_enabled   false
job_cancel_ontimeout          true
local_definition_labels
mode                          command_line
output_item_sort_criteria     byname
show_hidden                   false
default_az_subscription_id
default_az_resource_group
default_az_location
default_az_admin
default_capacity
default_open_experience       fabric

Expected Behavior

If workspace_private_links_enabled is documented or listed as an available configuration key, it should be possible to set it via:
fab config set workspace_private_links_enabled true

Actual Behavior

The CLI returns:
[InvalidInput] 'workspace_private_links_enabled' is not a known configuration key

Additional Context

The setting workspace_private_links_enabled is referenced as an available configuration option, but it is:

• Not recognised by the CLI when setting it
• Not shown in the output of fab config ls

This suggests one of the following:

• The setting is not yet implemented in the CLI
• The setting is restricted to a specific mode/environment
• There is a mismatch between documentation and CLI support

Possible Solution

No response

[github-actions]

AI Assessment: Potential Bug

Analysis:
The error indicates that workspace_private_links_enabled is not recognized as a supported configuration key in the CLI (fab config set). Your output from fab config ls does not list this setting, suggesting it is neither exposed nor implemented in configuration handling as of version 1.6.1. While network isolation and Private Link support are critical features, there is no reference in official CLI documentation that this setting exists or can be altered through fab config set (see: config commands). If documentation or other product guidance advertises this feature, the CLI implementation appears to be lagging or inconsistent.

Impact:
This blocks the ability to enable Private Link features via CLI for enterprise use cases, affecting deployment automation and compliance workflows. The mismatch between documentation/expectations and actual CLI capability warrants investigation to determine if this setting should be available and implemented, or if documentation needs clarifying.

Next Steps:
🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

[github-actions]

🔔 @microsoft/fabric-cli-dev — This issue has been flagged by AI triage as requiring team attention. Please review the assessment above.

[mkufa]

AI Assessment: Potential Bug

Analysis: The error indicates that workspace_private_links_enabled is not recognized as a supported configuration key in the CLI (fab config set). Your output from fab config ls does not list this setting, suggesting it is neither exposed nor implemented in configuration handling as of version 1.6.1. While network isolation and Private Link support are critical features, there is no reference in official CLI documentation that this setting exists or can be altered through fab config set (see: config commands). If documentation or other product guidance advertises this feature, the CLI implementation appears to be lagging or inconsistent.

Impact: This blocks the ability to enable Private Link features via CLI for enterprise use cases, affecting deployment automation and compliance workflows. The mismatch between documentation/expectations and actual CLI capability warrants investigation to determine if this setting should be available and implemented, or if documentation needs clarifying.

Next Steps: 🔔 Escalated to team — This issue requires team review and has been flagged for attention.

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

It is listed under "Available Settings" https://microsoft.github.io/fabric-cli/essentials/settings/

[ohadedry]

@mkufa

We would appreciate your input in order to investigate this issue further:

1. This exact error string doesn't exist in the 'config set' flow.
   Did you get something like the following?
   "[InvalidInput] <key_name> is not a recognized configuration key. Please check the available configuration keys"

2. You mentioned that you are using version 1.6.1, did you upgrade Fabric CLI from previous version or was it installed without any prior version?

3. According to CLI mode, the mode is interactive mode but according to "Steps to Reproduce" it is command line mode. Which mode reproduce the issue?

[ohadedry]

/needinfo

[microsoft-github-policy-service]

@mkufa, we require additional information to properly evaluate this issue.
Please provide the requested details so we can continue with the review process.