Federated IDs - Create Directory not available

[Bernhard23034626qnlz]

Hello,

we are trying to migrate our users to Federated IDs and therefor try to create the federated directory according https://helpx.adobe.com/enterprise/using/set-up-identity.html

Our problem is that there is no button called “Create Directory”. Are we missing something?

best regards

[iCharles]

Hello there,

We have reviewed your account which you have utilised to post here and found that you are using a Creative Cloud Teams subscription. 

Federated ID's are specific to Creative Cloud Enterprise, hence you will not see Create Directory button in the Admin Console. 

To know more about it and the difference between different types of Identittes, please read the following help document: Identity Types.

[Bernhard23034626qnlz]

Thank you for your response.

Is there any way to migrate to Creative Cloud Enterprise?

[Vikrant R · Accepted solution]

You'll need to contact Adobe Sales or Support to help you find a solution that works best for you. You could contact Support by using the available options on the Admin Console > Support page.

Alternatively, you may review the offering highlights here and then contact Adobe Sales: https://www.adobe.com/howtobuy/buying-programs/enterprise.html

[Bernhard23034626qnlz]

Thanks to clarify this.

In this case I need to talk to our purchasing department.

[derekc22870598]

Hi, I'm just running into this same issue. How is Federated IDs with SSO not available with Creative Cloud for Teams? It's 2022. SSO is a requirement for any business, period. The additional features (and cost) of Enterprise should not be needed to add Federated ID and SSO support.

[Bernhard23034626qnlz]

Yes, it is very odd that this is not supported for Teams and we also decided that the upgrade is not worth it.

Just putting https://sso.tax here as reminder why SSO should be possible in 2022.

[AlphaGeekBoy]

@Vikrant R & @iCharles  - I just came across this, and it would be helpful if this information were included in the Prerequisites section on each setup instruction for Federated Id. For example, I saw the banner about migrating my IDs, clicked on the link, and looked at the options. I decided that Federated made the most sense. I then found the Google Federation Sync page and tried to follow the instructions, and like @Bernhard23034626qnlz discovered the Create Directory option was missing.

I then started investigating to see if I was missing something in the instructions or if something else was configured incorrectly. I even double-checked the prerequisites that I met the requirements. After about 30 minutes, I Googled the issue and came across this post, which immediately answered my question.  Users managing SaaS for their organization are extremely busy and appreciate any time we can save.

I agree with @derekc22870598 that Enterprise's additional features (and cost) should not be needed to add Federated ID and SSO support.

[kglad]

open the support tab on your admin console > start chat or start case or request expert session.

https://helpx.adobe.com/enterprise/using/support-and-expert-services.html

[AlphaGeekBoy]

Thanks @kglad but don't really need support. Primarily just wanted to provide feedback on missing documentation. I don't have time to open a support ticket for this so providing it here in hopes that the Product Managers review.

[kglad]

better to do that here, for applicable apps, use https://helpx.adobe.com/ie/x-productkb/global/how-to-user-voice.html

for others, use https://www.adobe.com/products/wishform.html

[ICT5C7C]

2023 and still a thing.

This is a default feature on a lot of products nowadays, even loads of free plugins for wordpress etc.

Security (and central management) features, such as federated logins, sync and SSO should be included in all business packages, not only enterprise.

[NA24904885or5l]

Agree with the above. Needs to be included in the documentation for the prerequisites for SSO, Adobe can fill in the wishform themselves I don't have the time to waste.

[Paul38023655i3is]

More than a year later in 2024 and it's still a thing. I've been working on migrating all company services to SSO and was happy to see Adobe supported it. I guess they don't. Forcing a customer to pay MORE for what should be a base level business feature is wrong.

[iCharles]

Hi @Paul38023655i3is,

I understand your frustration regarding the additional cost of enabling SSO with Adobe services.

For setting up identity and Single Sign-On (SSO) in Adobe's Enterprise environment, here are some key points:

1. Adobe supports SSO through Federated IDs, which are linked to your enterprise directory.
2. Popular identity providers such as Microsoft Azure AD and Google can be used for SSO.
3. Detailed instructions for setting up and managing SSO with different identity providers are provided.
4. The setup and management of SSO require administrative control and proper configuration.

However, SSO is not a default feature for all subscriptions and might require specific plans.

For more information & detailed steps, refer to our help document: https://adobe.ly/3RmtA3q

^CS

[supportg69194040]

Roughly a year later and they still choose to lock SSO behind their Creative Cloud Enterprise licensing.

Nitro is looking better and better.

[derekc22870598]

Hi @iCharles 

Thanks for responding. The issue really seems to be that it appears creating a federated ID will be enough to support SSO. Until you try to set it up, find out it won't work, then find out that Acrobat TEAMS licensing does not support SSO. You need to pay extra for Acrobat ENTERPRISE if you want to combine federated IDs with SSO.

When the reality is, we don't need any of the other "Enterprise" functionality of Acrobat - we just want to use SSO to maintain a secure environment and simplify things for our users. SSO is here to stay and should included with any "Business" tier of licensing. Please provide feedback if there is any way to do so. Cybersecurity is extra important these days and forcing businesses to pay even more to use what should be basic functionality is just a painful sting on top of the already expensive new subscription costs.

Thanks for listening. I'm happy to provide additional commentary if there is anyone who can actually do something about this problem that will listen.

[Anshul_Nautiyal]

Hi @derekc22870598,

Thank you for taking the time to share your detailed feedback.
We truly appreciate you highlighting your experience and concerns regarding SSO functionality with Teams licensing. I will share your feedback with the relevant teams for further review and consideration.

If there are any updates or additional guidance available, we’ll be sure to let you know.

Regards,
^AN

[Jason29655907dnnv]

You'll have to pay the SSO Tax by upgrading to Enterprise just to secure your employees data with this best practice. They understand no other features are necessary, but this is a great way to increase profits for a security feature that should be included. But, good luck trying to reach a human being to secure your upgrade to enterprise. Please don't use chat as it appears completedly broken. Thanks.

[andrew_1281]

Unreal, How in 2025 is SSO an optional Add-on only associated with an Enterprise license?

This is increadibly backwards and dissapoint behaviour from a Security perspective as well as obstracting all of the good work around Self Service Purchasing of licenses.

Do better.

[WP22828408vx8c]

It's Adobe, did you expect something better?  Confirming August 2025 that this is still an Adobe problem.  I mean sure they discontinued Perpetual licensing with Adobe Acrobat 2020, and sure their subscription pricing means you'll spend twice as much as what you did before, and sure their customer service is outsourced to the cheapest bidder, but on the positive side....um..I got nothing.  Enterprise or Teams... Pay up to use an option that is considered normal security practice by almost every other software company.