Microsoft has officially ended production of the Azure Kinect DK, marking the end of an era for one of the most popular developer depth cameras. If your project relies on Azure Kinect hardware or SDKs, now is the time to plan your migration.
Timeline
- Microsoft announced the discontinuation with immediate effect on new hardware sales
- Existing SDK and firmware support will continue for a limited transition period
- No new features or hardware revisions will be released
Top Migration Options
1. Orbbec Femto Bolt — Official Microsoft-Recommended Replacement
Co-developed with Microsoft, the Femto Bolt uses the same ToF depth engine as Azure Kinect DK. It offers a drop-in migration path with compatible depth modes and similar API structures. Orbbec provides detailed migration documentation specifically for Azure Kinect users.
2. Orbbec Femto Mega
For applications requiring a wider field of view, the Femto Mega extends the same ToF technology with 120-degree coverage and built-in NVIDIA Jetson processing.
3. Intel RealSense D455 / D435i
For projects that can switch from ToF to stereo depth, Intel’s RealSense lineup offers mature SDKs and broad community support. The D455 provides longer range, while the D435i includes an IMU for motion tracking.
Migration Checklist
- Audit all Azure Kinect API calls in your codebase
- Test depth data format compatibility with your chosen replacement
- Update calibration parameters and coordinate system transformations
- Verify body tracking SDK compatibility (or switch to MediaPipe / OpenPose)
- Plan hardware procurement lead times
The discontinuation of Azure Kinect DK is a significant shift, but the depth camera ecosystem has matured considerably since its launch. Developers now have more options than ever, many offering superior performance at lower cost.
Leave a Reply