NOTE: Uniconta A/S does not provide support for Microsoft Assure AD, "Two-factor authentication".
NOTE: Only the owner of the accounts can correct / delete the AD setup in Uniconta.
Read the recommendations for creation here...
NOTE: Do not write owner on a company that has Azure setup on the subscription.
Once this is done, you need to do the following
Change owner to back to original owner
Then the original owner must remove AD from their subscription.
Now the new owner can be added to the company.
After this the AD can be put on the subscription again
Microsoft Azure provides two factor authentication (Multi-Factor Authentication MFA) which is easy, convenient and secure.
https://www.uniconta.com/da/video/generelt/sikkerhed-og-azure-i-uniconta/
Register an app in Azure
To create an app inside Microsoft Azure, go to https://portal.azure.com/ and sign up/ sign in with your Microsoft account.
Once you are inside the portal, go to Azure Active Directory
Inside App registrations, create a"New registration"
Inside Register an application, type a Name, choose an appropriate option for Supported account types & Redirect URI (Not to be used in Uniconta). Click on Register.
After successful App registration, you will find the new app inside App registrations screen.
To get the Application (client) ID & Directory (tenant) ID, open the newly created app and copy these details. Here Directory (tenant) ID will always be same for all your apps and Application (client) ID will be different.
Add Azure IDs to Uniconta
To add the above details in Uniconta, go to Uniconta App > Company > Maintenance > Subscription > Azure Details. Paste your Azure Client ID & Azure Tenant ID. Click Save.
Upon successfully saving. Next time when logged into Uniconta, the screen of authentication will popup.
Once authenticated, this screen of authentication will not appear again until the token expires.
Questions and answers
We've experienced that Odata didn't quite work on a single user when retrieving data from Uniconta.
It turned out that AD needed to be reactivated on the user. The customer had another user with different access problems. The same solution could be used here.
If you have similar experiences, this might be the solution.