If your Dynamics 365 Business Central tenant is setup to authenticate with Active Directory with 2FA, follow the steps below to setup an OAuth token:
1. Navigate to portal.azure.com
2. Search for App registrations in the top search bar and select App registrations.
3.Click New Registration and enter a name for the application.
4. Choose the appropriate Supported Account Type, most companies will use "Accounts in this organizational directory only"
5. For the Redirect URL, choose Web and enter: https://eoneconnectorauth.azurewebsites.net/Callback
6. Click Register
7. Click "Certificates & Secrets" in the navigation on the left.
8. Click "New client secret"
9. Give the secret a description and choose how long you want the secret to last. It is important to note that when the secret expires any connections using this secret will no longer connect successfully until a new secret is generated and used in the connection. Make sure to have a process in place for someone to create another secret and update any Popdock connections prior to the secret expiring in the future.
10. Click Add to generate the new secret. Copy and save the value somewhere as it will not be fully visible once you navigate away from the Azure Portal.
11. Click on “API Permission” in the navigation bar on the left.
12. Click “Add a permission” and choose Dynamics 365 Business Central.
13. Select Delegated permission if it is not already and enable user_impersonation and Financials.ReadWrite.All and click Add permissions.
14. Click on Overview in the navigation bar on the left.
15. Copy and save the “Application (client) ID” value.
16. With the Application ID and the Secret Value copied and saved from the application setup, the BC connection in Popdock can now be configured.
1. Open up Business central and click the ‘?’ help and support icon in the top right corner, scroll down to “Report a problem”. Copy your Azure AD Tenant value and Environment value.