Agentforce for Developers access/permission issue

[tillaffolter]

Summary

Agentforce for Developers is for some unknown reason not working in our production Org.
As far as I understand documentation (see https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/einstein-setup.html), Agentforce for Developers is enabled by default but strangely the option to disable/enable it in the setup of out Org is missing.
It is an Enterprise edition Org which is not in the EU Operating Zone and we have Einstein Generative AI turned on.
In the VS Code extension the error message "We couldn’t access Agentforce for Developers. Open an issue and we’ll get you the help you need." is displayed.
If I use a personal Dev Org, Agentforce for Developers works on the same machine with the same VS Code + Salesforce extensions setup.

Steps To Reproduce:

1. Authorize Salesforce production Org in VS Code

Expected result

Agentforce Dev Assistant in VS Code is ready to be used with our production Org

Actual result

Error message "We couldn’t access Agentforce for Developers. Open an issue and we’ll get you the help you need." is displayed in VS Code

Additional information

Salesforce Extension Pack Version in VS Code: 62.9.1

Salesforce Agentforce For Developers Version in VS Code: 1.5.0

OS and version: macOS Sequoia 15.1.1

VS Code version: 1.96.0

[klewis-sfdc]

Hi @tillaffolter,

Thank you for reporting the issue and including the screenshot! As a first step, do you know if this org has Multi-Factor Authentication enabled?

[tillaffolter]

Hi @tillaffolter,

Thank you for reporting the issue and including the screenshot! As a first step, do you know if this org has Multi-Factor Authentication enabled?

@klewis-sfdc Yes, MFA is enabled for all users' UI access to the Org, including mine. It's handled by our SSO provider's MFA service.

[klewis-sfdc]

OK, thank you for confirming, @tillaffolter. Unfortunately, there is some configuration of MFA that blocks access to A4D. This does not happen for all orgs with MFA enabled, but it does happen for some and we currently do not have a known workaround, aside from trying a different org or disabling MFA.

I have created this issue and pinned it to the repo, hopefully it will be helpful for the next User who runs into this scenario.

Once we understand more about the specific MFA configuration that causes this issue, we will update the pinned issue with details. Thank you.