Dynamics 365 F&O logo

Dynamics 365 F&O

ERP & FinanceOAuth 2.0Live

Connect your customers' Dynamics 365 Finance and Operations environments so your product can read and write OData entities across their legal entities. The customer's admin consents on Microsoft's screen; Askel stores the environment base URL, the aadTenantId, and the dataAreaId for each legal entity.

What you can do

Read customers and their ledger accounts

Fetch Customer entity records including account number, name, customer group, currency, and payment terms from the customer's D365 F&O environment.

Create and read sales orders

POST SalesOrderHeader and SalesOrderLine entities to create sales orders in the target legal entity, or read open orders filtered by customer account, status, or date range.

Read vendor and purchase order data

Fetch vendor master records and purchase order headers and lines. Useful for procurement-visibility workflows that need to surface open POs or receipt status from F&O.

Access ledger journals and account structures

Read the chart of accounts and posted general ledger transactions for financial reporting or reconciliation workflows that need actual ledger data from F&O.

Read inventory and product master data

Fetch released product records with item numbers, descriptions, unit of measure, and storage dimension assignments so your product can map SKUs without a separate data export.

Fetch worker and HR data

Read Worker entity records with employment status, department, and position for HR-integrated onboarding workflows that need to cross-reference employees between your product and F&O.

Sample use case

Syncing confirmed sales orders from your CPQ tool to D365 F&O

You sell a configure-price-quote (CPQ) platform. A new customer, Vantage Industrial Solutions, uses D365 Finance and Operations for order management and fulfilment. When a quote is accepted in your CPQ tool, Vantage wants a confirmed sales order to appear in their F&O environment automatically, scoped to the correct legal entity (VIS-UK).

  1. 1

    Admin consents and provides environment details

    Vantage's IT admin clicks Connect Dynamics 365 F&O in your product. Askel redirects to Microsoft's consent screen. After approval, the admin provides their environment base URL (vantage.operations.dynamics.com) and the legal entity code VIS-UK. Askel stores all three values.

  2. 2

    Product catalog mapping

    Askel reads the released products from the F&O environment scoped to the VIS-UK legal entity. Your CPQ tool's admin maps each CPQ product code to the matching F&O item number. Unmatched products are flagged for manual resolution.

  3. 3

    Customer account lookup

    When a quote is accepted for a named buyer, Askel checks whether a matching customer account exists in F&O by querying the Customers entity with the buyer's name or external reference. If no match is found, Askel creates a new customer account.

  4. 4

    Sales order created

    Askel POSTs a SalesOrderHeader and SalesOrderLine set to the F&O OData endpoint, with dataAreaId=VIS-UK on the request. The order header includes the customer account, requested ship date, and delivery address from the CPQ quote.

  5. 5

    Order number stored

    F&O returns the new order number. Your CPQ tool stores it on the quote record and displays it to Vantage's sales rep as confirmation. Vantage's order management team sees the order in F&O immediately and begins the fulfilment process.

Authentication

OAuth 2.0

The customer's Microsoft admin consents on the standard Microsoft identity platform screen. Askel stores the refresh token, the aadTenantId (read from the token claims), the environment base URL, and the dataAreaId (legal entity code) provided by the customer. Every OData request is sent to the environment base URL with the dataAreaId in the request body or query where required. Access tokens are minted per request and expire after one hour.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's D365 F&O environment, Askel, and Your productCustomer's D365 F&O environmentAPI endpointAskelauth · mapping · driftYour productyour backend
CustomersSales ordersVendorsReleased productsLedger accountsWorkers

FAQ for Dynamics 365 F&O

Does this work for Dynamics 365 Finance standalone as well as F&O?+
Dynamics 365 Finance and Dynamics 365 Supply Chain Management share the same OData API surface and the same Azure AD authentication. Askel works with both. The specific entities available depend on which apps and modules the customer has licensed.
What if the customer has multiple legal entities?+
Each legal entity has its own dataAreaId. A customer with multiple legal entities can have multiple Askel connections under the same customer record, each pointing to a different dataAreaId. Your product targets the correct connection per workflow.
What Azure AD permissions are needed?+
The consenting user needs the Dynamics 365 Finance permission in Azure AD (user_impersonation on the ERP service principal) plus a valid F&O user account with the system administrator or appropriate role for the entities your integration reads or writes.
Can we use application permissions (daemon/service) instead of delegated permissions?+
Yes. D365 F&O supports application-level OAuth using a registered Azure AD app with an application permission grant instead of user delegation. If your use case requires unattended access without a logged-in user, the customer can register an app in Azure AD and provide Askel with the client ID, client secret, and tenant ID instead of going through the user consent flow.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.