microsoft-dynamics-hr

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: microsoft-dynamics-hr
description: |
  Microsoft Dynamics 365 Human Resources integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Microsoft Dynamics 365 Human Resources. Routes through Apideck with serviceId "microsoft-dynamics-hr".
license: Apache-2.0
alwaysApply: false
metadata:
  author: apideck
  version: "1.0.0"
  serviceId: microsoft-dynamics-hr
  unifiedApis: ["hris"]
  authType: oauth2
  tier: "2"
  verified: true
---

# Microsoft Dynamics 365 Human Resources (via Apideck)

Access Microsoft Dynamics 365 Human Resources through Apideck's **HRIS** unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single `serviceId` string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Microsoft Dynamics 365 Human Resources plumbing.

## Quick facts

- **Apideck serviceId:** `microsoft-dynamics-hr`
- **Unified API:** HRIS
- **Auth type:** oauth2
- **Apideck setup guide:** [Connection guide](https://developers.apideck.com/connectors/microsoft-dynamics-hr/docs/consumer+connection)
- **Gotchas:** [page](https://developers.apideck.com/apis/hris/microsoft-dynamics-hr/gotchas)
- **Microsoft Dynamics 365 Human Resources docs:** https://learn.microsoft.com/dynamics365/human-resources/
- **Homepage:** https://dynamics.microsoft.com/en-us/human-resources/

## When to use this skill

Activate this skill when the user explicitly wants to work with **Microsoft Dynamics 365 Human Resources** — for example, "sync employees in Microsoft Dynamics 365 Human Resources" or "list time-off requests in Microsoft Dynamics 365 Human Resources". This skill teaches the agent:

1. Which Apideck unified API covers Microsoft Dynamics 365 Human Resources (HRIS)
2. The correct `serviceId` to pass on every call (`microsoft-dynamics-hr`)
3. Microsoft Dynamics 365 Human Resources-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

- [`apideck-node`](../../skills/apideck-node/), [`apideck-python`](../../skills/apideck-python/), [`apideck-dotnet`](../../skills/apideck-dotnet/), [`apideck-java`](../../skills/apideck-java/), [`apideck-go`](../../skills/apideck-go/), [`apideck-php`](../../skills/apideck-php/), or [`apideck-rest`](../../skills/apideck-rest/)

For the raw OpenAPI spec:

- **HRIS:** [https://specs.apideck.com/hris.yml](https://specs.apideck.com/hris.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=hris)

## Minimal example (TypeScript)

```typescript
import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List employees in Microsoft Dynamics 365 Human Resources
const { data } = await apideck.hris.employees.list({
  serviceId: "microsoft-dynamics-hr",
});
```

## Portable across 58 HRIS connectors

The Apideck **HRIS** unified API exposes the same methods for every connector in its catalog. Switching from Microsoft Dynamics 365 Human Resources to another HRIS connector is a one-string change — no rewrite, no new SDK.

```typescript
// Today — Microsoft Dynamics 365 Human Resources
await apideck.hris.employees.list({ serviceId: "microsoft-dynamics-hr" });

// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "workday" });
```

This is the compounding advantage of using Apideck over integrating Microsoft Dynamics 365 Human Resources directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes