Share via

how to run Microsoft Project Olympus SP3 server at home

mk-1 0 Reputation points
2026-06-10T22:05:40.9066667+00:00

hello

I am evaluating a Microsoft Project Olympus server platform based on a Quanta SP3 motherboard designed for AMD EPYC 7001 (Naples) processors, and I am trying to better understand the hardware requirements for operating this system outside of its original Azure/OCP rack environment.

From the information I have found, the motherboard appears to use a 12V-only power design rather than a standard ATX power supply. However, I have not been able to determine whether the system can be powered directly from a generic 12V server PSU or whether the original Olympus PMDU and associated management hardware are required.

I would appreciate any information regarding:

Power supply requirements for the Olympus SP3 platform

Whether the PMDU is mandatory for system startup

The role of management signals such as BLADE_EN# and PSU_ON#

BMC accessibility and management outside of an Azure rack environment

Known limitations regarding PCIe devices, GPUs, or firmware support

I am particularly interested in understanding whether these systems can be operated independently as standalone servers and whether there is any official documentation available describing the power sequencing and management interfaces.

Thank you for any guidance or documentation references.

Windows for business | Windows Server | Devices and deployment | Other
0 comments

Answer accepted by question author

HLBui 6,675 Reputation points Independent Advisor
2026-06-10T23:44:37.6866667+00:00

Hi mk-1 ,

The SP3 board runs on a 12V-only design, so you can’t just drop in a regular ATX PSU. A generic 12V server PSU can technically provide the juice, but the tricky part is the power sequencing and control signals that the original PMDU handled. Without that unit, you’ll need to replicate signals like BLADE_EN# and PSU_ON#, otherwise the board may not even get past initial startup.

On the BMC side, you can still reach it outside of Azure racks, but don’t expect the same polished tooling you’d see in Microsoft’s environment. It’s functional, but some features are tied to Azure-specific hooks, so you’ll be working with a more barebones interface. As for PCIe and GPUs, compatibility is mixed - some firmware builds don’t fully support add in cards, and GPUs in particular can be finicky depending on BIOS and firmware revisions. That’s why folks often report “works with some cards, fails with others.”

Now, about standalone operation: yes, it’s possible, but it’s not plug-and-play. You’ll need to be comfortable wiring up power sequencing and possibly hacking around management signals. Official documentation is limited - most of what’s out there is in OCP specs and community notes rather than polished manuals. So, while you can get these boards running independently, they were really designed to live inside the Azure/OCP ecosystem, and you’ll feel that when you try to run them solo.

In short: doable, but expect some tinkering and limitations.

If everything is okay, don't forget to share your experience with the issue by "Accept answer". If you need more information, feel free to leave a message. We are happy to help!

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.