Azure NP10s custom xclbin rejected - xclbin is invalid please provide azure xclbin

Hello Supraja,

Thank you for reaching out on Microsoft Q&A

From what you’ve described, the error “xclbin is invalid, please provide azure xclbin” (Error -2060) is occurring because the bitstream was not built and processed in a way that’s compatible with Azure NP-series FPGA requirements. Your VM is running an Azure-specific shell, but the .xclbin appears to have been compiled using a standard Xilinx platform, and the static UUID in the binary is empty. Due to this mismatch, Azure is rejecting the bitstream.

On Azure NP-series VMs, custom bitstreams cannot be used directly. They must be built using the Azure-specific platform and then validated through the Azure FPGA Attestation Service, which signs the design before it can be loaded onto the FPGA.

To resolve this issue, please ensure you are using the Azure-specific platform (.xpfm) corresponding to your shell (xilinx_u250_gen3x16_xdma_shell_2_1) instead of the standard U250 platform. The required platform and deployment packages can be downloaded from the AMD/Xilinx Microsoft Azure page:

https://www.amd.com/en/where-to-buy/accelerators/alveo/cloud-solutions/microsoft-azure.html

When compiling with Vitis v++, include the following flag to produce a netlist (DCP) output — this is required by the Attestation Service and without it, your submission will be rejected:

--advanced.param compiler.acceleratorBinaryContent=dcp

Upload your .xclbin to an Azure Blob Storage container and submit it to the attestation service. Once validation is successful, the service will return two files:

Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/field-programmable-gate-arrays-attestation

https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/fpga-accelerated/np-series?tabs=sizebasic

To help us assist you further, could you please confirm the following:

Which exact .xpfm platform file are you currently using for the build?

Did your v++ build command include --advanced.param compiler.acceleratorBinaryContent=dcp?

Have you already submitted the .xclbin to the Azure FPGA Attestation Service? If yes, were any error logs (error-*.txt) written back to your blob container?

Can you share the output of xbutil examine from your VM?

Can you share the exact v++ command used to generate the .xclbin?

Thank you for the detailed response. Here are the answers to your questions:

1. Platform file currently used:

/opt/xilinx/platforms/xilinx_u250_gen3x16_xdma_2_1_202010_1/xilinx_u250_gen3x16_xdma_2_1_202010_1.xpfm

This is the only platform file installed on the VM. The shell on the card reports as xilinx_u250_gen3x16_xdma_shell_2_1 (UUID: C3AD6B03-7144-8CA9-494E-D5B672C7092A), which is different from the platform name. We believe this is the root cause — the installed platform does not embed the correct shell UUID, resulting in Static UUID: 00000000-0000-0000-0000-000000000000 in the xclbin.

2. Yes, the current rebuild includes the flag:

--advanced.param compiler.acceleratorBinaryContent=dcp

The build is currently in progress (full place and route running).

1. Not yet submitted to the attestation service. We have registered for the preview at aka.ms/AzureFPGAAttestationPreview using:

Awaiting approval. Will submit once the build completes and access is granted.

4. xbutil examine output:

Shell: xilinx_u250_gen3x16_xdma_shell_2_1

Platform UUID: C3AD6B03-7144-8CA9-494E-D5B672C7092A

BDF: [0001:00:00.0]

Device Ready: Yes

XRT Version: 2.13.479

5. Exact v++ command used for current rebuild:

v++ --link \

--target hw \

--platform xilinx_u250_gen3x16_xdma_2_1_202010_1 \

--config connectivity.cfg \

--advanced.param compiler.acceleratorBinaryContent=dcp \

--optimize 3 \

-o jaccard_netlist.xclbin \

jaccard_kernel.xo
```Follow-up question:

The AMD Azure page you linked mentions downloading an Azure-specific platform. Is the platform xilinx_u250_gen3x16_xdma_2_1_202010_1 correct for Azure NP10s attestation, or do we need a different .xpfm file that embeds the Azure shell UUID (C3AD6B03)? If a different platform package is required, could you point us to the exact download link or package name?

Thank you.

Thanks for the update!

This issue is expected on Azure NP‑series VMs. Even though xilinx_u250_gen3x16_xdma_2_1_202010_1 is the correct platform, Azure does not allow loading raw xclbin files directly. Any custom xclbin must first be submitted to the Azure FPGA Attestation Service, which signs it and embeds the correct Azure shell UUID. Until then, the xclbin will be rejected with error -2060.

Also, please make sure you have installed the Azure-specific packages on your VM before the rebuild completes:

• xrt_202210.2.13.479_20.04-amd64-azure.deb
• xilinx-u250-gen3x16-xdma-validate_2.1-3005608.1_all.deb

Both can be downloaded from this link: https://www.amd.com/en/where-to-buy/accelerators/alveo/cloud-solutions/microsoft-azure.html

Both required packages are confirmed installed:

• xrt-azure 2.13.479
• xilinx-u250-gen3x16-xdma-validate 2.1-3005608.1

Netlist xclbin built with --advanced.param

compiler.acceleratorBinaryContent=dcp

Uploaded to blob storage :

https://fpgajaccardstorage.blob.core.windows.net/

jaccard-xclbin/jaccard_netlist.xclbin

Attestation preview request submitted at

aka.ms/AzureFPGAAttestationPreview for:

No approval email received after 24 hours.

Could you please check the status or directly

provide access to the attestation service?

We are fully ready to submit.

Hello Supraja,

Thank you for your patience and for providing all the required details. We can confirm that your environment is correctly configured, and you are fully prepared for the attestation process.

We have engaged internally with the relevant team regarding your request for access to the Azure FPGA Attestation Service.

We understand that your preview request submitted via the onboarding form has been pending for over 24 hours. At this time, our internal teams are actively working with the Product Management team to review the attestation onboarding process and access requests. We have also raised this as a priority due to the current blocker.

We expect to receive a concrete update along with next steps by Friday, and we will share the information with you as soon as it becomes available.

Important Update: NP-Series VM Retirement:

In parallel, we would like to bring an important service update to your attention. Azure NP-series Virtual Machines (Standard_NP10s, Standard_NP20s, and Standard_NP40s) are scheduled for retirement on 31 May 2027.

• You may continue using these VMs without impact until this date.
• After 31 May 2027, any remaining NP-series VMs will be deallocated, including those under Reserved Instance agreements.

Recommended action:

To avoid service disruption, to a product that meets your workload requirements before 31 May 2027.

Recommended alternatives for NP-series workloads: NDv2, NCads_H100_v5, and NCasT4_v3 VMs. For additional sizing guidance and workload alignment, please review our GPU VM documentation.

Additionally, could you please check the private message and provide necessary details.