Skip to main content

Troubleshooting SAML Single Sign On During Login

Learn how to resolve CloudExtend login issues when your organization uses SAML SSO

Updated yesterday

CloudExtend uses NetSuite’s secure 3-Step Authentication process.
NetSuite determines how you authenticate (SSO, basic credentials, or token-based auth) based on:

  • Your previous login method

  • Whether your role is SSO-enabled

  • Whether your organization has SSO configured correctly

Because of this, some users may experience login issues depending on the role they choose or their SSO settings.

Use the troubleshooting steps below based on your scenario.


Determine Your Use Case

Choose the section that applies to you:

Each scenario requires slightly different steps due to how NetSuite handles SSO vs non-SSO authentication.


Log in using Non-Admin and SSO Enabled Role

Follow these steps if you are a regular user and your role is allowed to authenticate via SSO.

Step 1: Sign in with Microsoft

Launch the CloudExtend app and click:

👉 Sign in with Microsoft

You will authenticate using your Microsoft 365 identity.

💡 Note:

Your CloudExtend login identity is now tied to Microsoft not NetSuite.
This means:

  • Once you login with your Microsoft account, you won't be asked to login again unless you clear cache.

  • You no longer need to sign out to switch NetSuite roles

  • You can connect to multiple NetSuite accounts under the same Microsoft login

  • You must always use the same Microsoft identity tied to your CloudExtend license

Step 2: Enter your NetSuite Account ID

In order to use the login flow, you will need your NetSuite Account Number. This can be located in the URL while you are logged into NetSuite in a browser. Learn how to find your NetSuite account ID here.

Example:
https://123456.app.netsuite.comAccount ID = 123456

Step 3: Use the Troubleshoot Link

You will see a “Troubleshoot SSO URL” link during login.
Click it and then enter the URL of your Identity Provider (IDP) for NetSuite.

Step 4: Enter the URL of your Identity Provider (IDP)

➡️ See the instructions for obtaining the URL.

A popup will validate:

  • Your SSO login

  • The NetSuite account

  • The role you will authorize

Close the window only after validation is complete.

❗️ If you have more than one NetSuite account be sure to navigate to the desired account before closing the window.

Step 5: Connect to NetSuite

  • This will bring you back to the login screen of CloudExtend.

  • When prompted enter your NetSuite Account ID and click Continue.

  • ​You should now be redirected to your SSO login page, not the standard NetSuite login page. Complete the login flow.

Step 6: Select your NetSuite Role

  • CloudExtend will present your available roles.

  • Choose your role → click Allow.

Step 7: You are now logged in!

💡 Note:

If you received an error here, it generally means your account does not have proper permissions. Ask your Admin to review the prerequisites here in our help center.


Log in using Admin or Non-SSO Role

NetSuite does not allow admins to log in with SSO. If your org has SSO set as the primary authentication method and you want to login to NetSuite as an admin via the 3-Step Authentication flow follow the steps below.

Step 1: Sign in with Microsoft

Launch the CloudExtend app and click:

👉 Sign in with Microsoft

You will authenticate using your Microsoft 365 identity.

💡 Note:

Your CloudExtend login identity is now tied to Microsoft not NetSuite.
This means:

  • Once you login with your Microsoft account, you won't be asked to login again unless you clear cache.

  • You no longer need to sign out to switch NetSuite roles

  • You can connect to multiple NetSuite accounts under the same Microsoft login

  • You must always use the same Microsoft identity tied to your CloudExtend license

Step 2: Enter your NetSuite Account ID

In order to use the login flow, you will need your NetSuite Account Number. This can be located in the URL while you are logged into NetSuite in a browser. Learn how to find your NetSuite account ID here.

Example:
https://123456.app.netsuite.comAccount ID = 123456

Step 3: Use the Troubleshoot Link

You will see a “Troubleshoot SSO URL” link during login.
Click it and then enter the URL of your Identity Provider (IDP) for NetSuite.

Step 4: Enter your NetSuite URL

Enter https://system.netsuite.com

If this does not prompt a login:

Use your full NetSuite dashboard URL instead:

https://123456.app.netsuite.com

⚠️ Replace 123456 with your account number.

A popup will validate:

  • Your SSO login

  • The NetSuite account

  • The role you will authorize

Close the window only after validation is complete.

❗️ If you have more than one NetSuite account be sure to navigate to the desired account before closing the window.

Step 5: Connect to NetSuite

  • This will bring you back to the login screen of CloudExtend.

  • When prompted enter your NetSuite Account ID and click Continue.

  • ​You should now be redirected to your SSO login page, not the standard NetSuite login page. Complete the login flow.

Step 6: Select your NetSuite Role

  • CloudExtend will present your available roles.

  • Choose your role → click Allow.

Step 7: You are now logged in!

💡 Note:

If you received an error here, it generally means your account does not have proper permissions. Ask your Admin to review the prerequisites here in our help center.


Obtaining the IDP URL for your NetSuite login using Microsoft Azure AD

If your Identity Provider is Microsoft Azure AD, use these steps:

Step 1: Go to https://myapplications.microsoft.com/ in your browser.

Step 2: Locate the NetSuite tile → click the ellipsis (…)

Step 3: Paste this link into the Troubleshoot SSO URL prompt in CloudExtend. This ensures CloudExtend redirects to the same SSO login page your organization uses.


Need Help?

If you still can't sign in after following the steps above:

💬 Chat with us (bottom-right)
📧 Email cloudextend-support@celigo.com

Please include:

  • Your NetSuite Account ID

  • Whether your role is SSO-enabled

  • Whether you are using Admin or a non-SSO role

  • A screenshot of where the login flow gets stuck

Did this answer your question?