Skip to content

IT access requirements

This page is for your IT or security team. It covers everything they need to enable before elevaite365 can run automated tests against your environment.

Share this page with IT

Everything here is a one-off setup. Send them this page. It's written for them, not for test authors.

Overview

elevaite365 runs your automated tests by logging into your D365 environment just like a real user, using a browser, a username, a password and MFA if you require it. Nothing needs to be installed.

Think of it as a short checklist for your IT team, so our virtual browsers can sign in safely and reliably:

Step What's needed
1 Allow our automation to sign in from our fixed IP addresses
2 Create 3 dedicated D365 test user accounts for workflows and approvals
2a Exclude those test users from mobile phone number registration
3 If you use MFA, configure it for app-based or TOTP-based methods (SMS and phone call are not needed)

We use our own TOTP logic

elevaite365 uses in-house TOTP logic, not Microsoft Authenticator or a standalone MFA app. Make sure software OATH/TOTP is enabled for these users in your tenant. See Microsoft's Manage authentication methods and software OATH tokens.

Step 1 · Network

Automated test traffic comes from a small set of fixed IP addresses. Allowlist the IPs for your region only, and only if your security policy requires it.

Region IP addresses
Australia 20.37.216.97
4.197.88.198
United States 4.155.240.150
20.115.135.55
Europe 135.220.28.64
135.220.222.42

Your region matches the URL you sign in at, see Setup your team.

Step 2 · Accounts

Create 3 dedicated test user accounts. These are automation accounts, not real employees, and they're used for workflows, approval chains and multi-user scenarios.

  • MFA is optional for non-production automation accounts
  • If using MFA, it works with our in-house TOTP logic, not Microsoft Authenticator or a traditional MFA app
  • Ensure software OATH/TOTP is enabled in your tenant's authentication methods policy
  • If using Conditional Access, scope it to your test user group
  • You may restrict sign-ins to your region's elevaite365 IPs

Never use a real person's account

Test users must be dedicated accounts. A real person's credentials in an automated test means locked accounts, unattributable activity and an audit problem.

Once the accounts exist, add them in the product, see Setup test users.

Step 3 · Final IT checklist

  • Create 3 test user accounts
  • Exclude them from phone number registration
  • If required, allowlist elevaite365 IPs for your region
  • MFA optional; if used, configure app or TOTP
  • Confirm the test users can log in successfully

How elevaite365 connects to your environment

A simplified view of how elevaite365 operates within our Azure tenant and interacts with your non-production D365 environment.

How elevaite365 connects to your environment Inside the elevaite365 Azure tenant, a Key Vault of encrypted test user credentials and an in-house TOTP service feed a pool of virtual browsers. Those browsers make outbound HTTPS connections only, from static regional IP addresses, to Entra ID authentication in your Azure AD tenant, which grants access to your D365 non-production environment. Conditional Access policies are optional and scoped to the test accounts. ELEVAITE365 AZURE TENANT Key VaultEncrypted test usercredentials In-house TOTP serviceGenerates softwareOATH/TOTP codes Virtual browser poolSecure containers thatrun your tests Outbound HTTPS only Static regional IP addresses YOUR AZURE AD TENANT Entra ID authenticationTest users with optionalsoftware OATH/TOTP D365 non-productionTarget environment forautomated test runs Conditional AccessOptional, scoped to testaccounts and our IPs

Traffic is outbound HTTPS only, from static region-specific IPs. Test user credentials are held encrypted in Key Vault.

Next: Setup test users