Use Your Windows / Office 365 Account to Login in (v. 2020.1)

The security system in v.2020.1 has been completely revamped. It is now based on OAuth2 / OpenID Connect security standards. This has many effects and benefits. One of the benefits is the quick adding (also in v.2020.1) of the first 3rd party identity provider - Microsoft Azure Active Directory (Azure AD).

Companies can now setup their ERP security domains to accept Azure AD logins. Azure AD is the Internet version of the popular Windows Domains. It is hosted (and secured) by Microsoft on behalf of the organizations.


The integration is with the so called "Work or school accounts". This is the Microsoft term for Azure AD accounts, hosted by Microsoft on behalf of the organizations. Currently, Microsoft personal accounts, are not supported.

By utilizing the Azure AD account sign-in, your company can benefit in the many ways, including:

  • Single Sign-On for your work accounts.
    Users no longer need to have separate passwords for the ERP and other work-related resources.

  • Use your existing security infrastructure.
    Directly utilize your Azure AD setup.

  • No longer store passwords in the ERP.

  • Directly apply domain security policies (MFA, complexity, etc.) to the login security of the ERP.

In the future, we will gradually add many more security providers. There are plans for Google, Facebook, Microsoft, Okta, Auth0 and many more.

You can setup multiple identity providers, including multiple Azure ADs, for a single ERP user domain. They can all be used simultaneously for user login. Upon login, the users will be able to choose a security provider to use for their login.

NOTE: v.2020.1 supports multiple ID providers, but only Azure AD is supported. However, multiple different organizational Azure ADs are supported.

Azure AD is multi-tenant security provider. The same is true for Okta, Auth0 and many other single sign-on identity providers. This means, that the same security handler (for example, Microsoft Azure AD) can store the domains for many organizations. In contrast, Microsoft personal accounts, Facebook, Google, etc. are single-tenant providers.

Starting with multi-tenant providers, in the future we will support both multi-tenant and single-tenant providers.

Also, in the future, as a central site and each organization (tenant) using will be able to act as a Single Sign-On Identity Provider for other apps.

To setup the Azure AD integration, refer to the documentation. Basically, you need to register your tenant in your Azure AD as application. Then, in the ERP, you need to create User Domain and then add Domain Provider for Azure AD with the registration codes, used in the Azure AD application registration. 

Have more questions? Submit a request


  • 2
    Aleksandar Tsvetanov


    Could you send an additional information how we can setup that kind of login - in Azure and then in We wants to use our Office 365 accounts to login.

  • 0
    Mariya Savova [Mania/M Holding].

    We are getting the below error message: "You can't use your Mania account to sign-in because license 'SEC01 - Security - Sign in with Azure AD' is not installed on the server."

    How we can install this license 'SEC01 - Security - Sign in with Azure AD'? 

  • 0
    Tihomira Ivanova [ERP.NET]

    Hello, Maria!

    Using the Microsoft login requires having a license "SEC01" activated for your server/database.

    You can contact our sales team to discuss the details.

    Best regards,


  • 0
    Ivan Argentinski []
Please sign in to leave a comment.
Powered by Zendesk