ENAME Agent for Microsoft Teams –

Publisher Documentation

Setup & First-Time Use

1. Overview

The ENAME Agent for Microsoft Teams is designed to assist institutional users in

seamlessly connecting their Legal Entity Identifier (LEI), trading portfolios, and

front-o?ice systems such as Aladdin, SimCorp, and CRD to the ENAME network. This

integration is accomplished while ensuring that portfolio data remains securely hosted

within the client’s own Microsoft 365 tenant, protected by an ENTRA-secured ENAME

agent.

This documentation provides a comprehensive guide that includes:

• Step-by-step instructions for first-time setup

• Guidance for Teams / M365 administrators on deployment and rollout

• High-level information for business users and stakeholders

2. Roles & Audience

• Teams / M365 Administrator

• Responsible for approving and deploying the ENAME Agent app and managing

permissions regarding who can install and use the application within the

organisation.

• ENAME / IT Owner (Front-O?ice Technology, Architecture, or Platform Team)

• Oversees the deployment and management of the ENAME tenant agent, ensures

connectivity with OMS/EMS systems, and manages ENTRA integration.

• End Users (Traders, PMs, Collateral / Treasury, Operations)

• Utilise the ENAME Agent to register portfolios, view associated ENAMEs, and

enable downstream workflows within their operational remit.

3. Prerequisites

Before running the ENAME Agent wizard for the first time, ensure the following

prerequisites are met:

1. Microsoft 365 / Teams

2. – Possess a valid M365 licence with Teams enabled.

3. – The ENAME Agent app must be permitted within the tenant (refer to section 4).

4. ENAME Environment

5. – Completion of ENAME subscription and onboarding.

6. – ENAME tenant agent is deployed and accessible through ENTRA-secured APIs.

7. Core IDs & Systems

8. – An active and known LEI.9. – A list of trading portfolios and their custodian references (e.g. JPM6576,

GS000987657, DAN34DT, BARC2299-0099).

10. – Availability and integrability of your Investment Management System / Order

Management System (ISM/OMS), such as Aladdin, SimCorp, or CRD, with ENTRA

authentication and FIX/WebSocket STP.

4. For Teams / M365 Administrators – Deploying ENAME Agent

1. Allow the App

2. Navigate to Teams admin centre > Teams apps > Manage apps. Search for

“ENAME Agent” and set the status to Allowed for your tenant.

3. Control Access

4. Go to Teams apps > Permission policies. Add ENAME Agent to the relevant

permission policy (such as “Front O?ice Apps”) and assign it to the appropriate

users or groups (e.g. traders, PMs, collateral, operations).

5. (Optional) Pin the App

6. Access Teams apps > Setup policies, add ENAME Agent to Pinned apps for

selected users, and apply the setup policy.

Direct users to this Publisher Document to serve as the o?icial guide for setup and

usage.

5. First-Time User Setup – Step-by-Step Wizard

When a user adds and opens the ENAME Agent in Teams for the first time, the following

steps are performed:

Step 1 – Add and Open the ENAME Agent

1. 2. 3. 4. In Microsoft Teams, click on Apps.

Search for “ENAME Agent” and select Add.

The ENAME Agent will open as a personal app.

If prompted, sign in using your organisation account (ENTRA ID) and grant the

necessary permissions.

Upon completion, the initial setup wizard will be displayed.

Step 2 – Link to Your LEI

1. 2. The wizard will prompt you to “Link your Legal Entity Identifier (LEI)”.

Enter or search for your LEI, either by code or by legal entity name, depending on

the configuration.

3. The ENAME Agent queries the ENAME database to validate your LEI and link it to

your tenant and ENTRA identity.

Once confirmed, this LEI serves as the foundational identity for your ENAME

configuration.

Step 3 – Enter Trading Portfolios (Custodian References)

1. Input the trading portfolios under your management, identified by custodian

references (such as JPM6576, GS000987657, DAN34DT, BARC2299-0099).

2. You may enter these references individually or submit a list, depending on the

enabled options.3. Upon submission, the ENAME Agent checks the ENAME database to determine

whether ENAMEs already exist for these portfolios under your LEI.

Step 4 – ENAME Lookup & Creation

The ENAME Agent processes each provided portfolio reference as follows:

• If an ENAME exists:

• Returns the existing ENAME identifier for the portfolio.

• Identifies the originating user who first registered it within your organisation.

A confirmation list is displayed, mapping each custodian reference to its ENAME and

owner/originator.

If it is a new trading portfolio:

Generates a new ENAME for the portfolio.

Stores the new ENAME within your tenant-based ENAME agent.

Links the ENAME to your LEI and ENTRA identity as the originator.

The newly created ENAME appears in the summary list.

By the end of this step, you have a clear mapping of your LEI, custodian portfolio IDs,

and their corresponding ENAMEs (both existing and newly created).

Step 5 – Connect to Your ISM/OMS via ENTRA

The next phase involves connecting the ENAME Agent to your Investment or Order

Management System (ISM/OMS), such as:

• BlackRock Aladdin

• SimCorp Dimension

• Charles River Development (CRD)

• Other OMS/EMS as configured

• The wizard prompts you to “Connect to your ISM/OMS”.

• Select your system from the available list.

• The ENAME Agent presents an ENTRA authentication URL or flow, which may

open a Microsoft sign-in window.

• You or your administrator may need to consent to the ENAME Agent accessing

the ISM/OMS integration API on behalf of the organisation.

Upon successful completion, the ENAME Agent will be able to securely access your

ISM/OMS application according to the granted permissions.

Step 6 – Establish FIX STP Connectivity (WebSocket)

With ENTRA authentication established, the ENAME Agent sets up FIX STP connectivity

between your ISM/OMS and the ENAME tenant agent, facilitating integration with the

ENAME network.

1. The ENAME Agent initiates a WebSocket/FIX session with your ISM/OMS.

2. It creates or confirms mappings between trading portfolio (custodian reference),

ISM/OMS portfolio/account, and ENAME identifier.

Once the connection is active, the system status will indicate, for example: “FIX STP:

Connected”.

Step 7 – Point the Agent to RFQ and Confirmation Ports

The ENAME Agent must be configured with the appropriate ports or endpoints for:1. RFQs (Request for Quotes): The agent is directed to the execution port used by

your ISM/OMS or trading infrastructure, enabling it to tag RFQs with the correct

ENAME and associate them with the respective trading portfolio.

2. FIX Trade Confirmations: The agent listens to the FIX confirmation port or stream

to receive trade confirmations and map them to the relevant ENAME and

portfolio.

3. NFT STP for Risk Updates: For workflows utilising tokenisation or NFTs, the

confirmation feed is used to trigger NFT STP, updating risk and exposure in the

ENAME representation in your tenant and, if configured, within your ISM/OMS.

During setup, you may be prompted to select from pre-configured endpoints or

manually enter endpoint names, URLs, or ports as provided by your IT team.

When configuration is successful, the wizard will display a status such as:

RFQ port: Connected

FIX confirm: Connected

NFT STP: Enabled

6. Ongoing Use in Teams

Following initial setup, users can access the ENAME Agent from the Teams left

navigation (if pinned) or via the Apps menu. Typical activities include:

• Viewing mappings between portfolios and ENAMEs

• Initiating straightforward optimisation or collateral workflows

• Monitoring ENAME-related events, such as matches and risk updates

For collaboration, users can share ENAME-related insights in Teams chats or channels,

provided the app o?ers message extensions or tabs.

7. Guidance for Admins and Stakeholders

Teams / M365 Admins

• Ensure the ENAME Agent is available to the required users.

• Pin the app for key roles when suitable (e.g. traders, PMs, treasury, operations).

• Reference this Publisher Document in any internal rollout or training materials.

ENAME / IT Owners

• Coordinate ENTRA app registration and consent processes.

• Oversee ISM/OMS integration and FIX/WebSocket connectivity.

• Manage RFQ and confirmation port configurations.

• Maintain monitoring and logging for the ENAME Agent and tenant agent.

• Develop and update documentation for internal users regarding ENAME

mappings and their significance.

Business Stakeholders

• Recognise that ENAME provides a stable, portfolio-level identity for workflows

across multiple systems.

• Understand that the ENAME Agent in Teams serves as a front-end access point,

not as a trading venue.• Utilise this document for training, change management, and to communicate

setup and data flows to governance and risk teams.

8. Support

For assistance:

• Teams app installation or access: Contact your internal Teams / M365 Admin.

• ENAME configuration, ISM/OMS integration, FIX/STP, or portfolio mappings:

Reach out to your ENAME platform owner or:

ENAME Support

info@ename.ai

A link to this Publisher Document can be included in your Teams Store listing and within

the ENAME Agent (e.g. via “Help → Publisher Documentation”) to provide both

administrators and users with a clear, high-level guide for deployment and first-time

use.