This guide walks you through generating the necessary API credentials in Microsoft Azure and connecting them to your Omikai environment so the system can send emails autonomously.

Phase 1: Generating Credentials in Microsoft Azure

To allow Omikai to send emails, you first need to register it as an authorized application within your Microsoft environment. You will need an IT Administrator with access to the Microsoft Entra admin center.

Step 1: Register the Omikai Application

1. Log in to the Microsoft Entra admin center.

2. In the left navigation menu, expand Identity (Entra Id) > Applications and select App registrations.

3. Click New registration.

4. Name: Enter a descriptive name (e.g., Omikai-ERP-Email).

5. Supported account types: Select Accounts in this organizational directory only (Single tenant).

6. Redirect URI: Leave this completely blank.

7. Click Register.

Step 2: Grant Email Permissions

1. In your newly created App Registration, go to the left menu and select API permissions.

2. Click Add a permission and select Microsoft Graph.

3. Select Application permissions (This allows Omikai to send emails in the background without a human logging in every time).

4. In the search bar, type Mail.Send.

5. Check the box next to Mail.Send and click Add permissions.

Step 3: Grant Admin Consent

1. On the API permissions page, look for the yellow warning status next to Mail.Send.

2. Click the Grant admin consent for [Your Organization] button above the permissions list.

3. Click Yes to confirm. The status will update to a green checkmark.

Step 4: Generate the Client Secret (The Password)

1. In the left menu of your App Registration, select Certificates & secrets.

2. Under the Client secrets tab, click New client secret.

3. Add a description (e.g., Omikai-API-Key) and choose an expiration window (e.g., 12 months). Click Add.

4. ⚠️ CRITICAL: Immediately copy the text in the Value column. This will disappear once you leave the page.

Step 5: Gather Your Three Connection Keys

Go to the Overview page of your App Registration. Copy the following three items to paste into Omikai:

• Tenant ID (Directory ID)

• Client ID (Application ID)

• Client Secret (The value you copied in Step 4)

Phase 2: Inserting Credentials into Omikai

Now that Microsoft has provided the keys, you will activate the connection inside the Omikai settings.

Step 1: System-Wide Configuration (Main Email)

This establishes the primary connection and sets up your main company sending address (e.g., info@omikai.com).

1. Log in to Omikai and navigate to Settings > Account in the left-hand menu.

2. Go to the Profile tab and open up the profile settings.

3. Locate the E-mail provider setting and select Microsoft Graph from the dropdown menu.

4. Scroll down and expand the Microsoft Graph settings section.

5. Paste the three keys you gathered from Azure:

   • Tenant ID

   • Client ID

   • Client secret

6. Sender e-mail: Enter the primary email address you want the system to send from (e.g., info@omikai.com).

Make sure your user settings reflect your profile settings (eg. both using Microsoft Graph)

Step 2: Individual User Configuration (Optional)

If you want individual staff members to be able to send emails through Omikai using their own personal company addresses, follow these steps for each user:

1. Navigate to Settings > User.

2. Select the specific user's profile.

3. Set their E-mail provider to Microsoft Graph.

4. Expand the Microsoft Graph settings for that user.

5. Enter their personal company email into the Sender e-mail field.

🛡️ A Brief Note on Security

Because this setup uses "Application Permissions," Microsoft grants Omikai the technical ability to send mail as any user in your organization by default.

• If you do nothing else: Phase 1 and Phase 2 will work perfectly out of the box for any email address you type into Omikai.

• Best Practice: If your IT team wants to strictly limit Omikai so it can only send from info@omikai.com (or a specific group of users), they will need to apply an "Application Access Policy" in the background using Exchange Admin tools.