Registering for Driver Attestation impossible?

History: We started with a Microsoft Entra ID account months ago to submit a Windows KMDF driver for attestation signing, i.e. participating in the Hardware developer Program. It took months to have a vetted account authorization, we now have green checks at all fields for the legal entity and assigned persons.

One Person is assigned to be the responsible developer having the Account setting "Hardware",

But if he is logged in and checks "Account settings -> Programs -> Registered Programs" the Hardware Program does not show up in the list,

Going to "Other Programs" to register for the Hardware Program leads to a "Dead End". After clicking the "Get started" Link on the Hardware section we get the following page which shows the message below, together with an everlasting load animation:

Clicking on "Contact your administrator" does not change anything, it simply does nothing..
We made numerous attempts to contact Microsoft but they all ended in getting referred to where we have been already.

Any ideas on how to solve this issue?

Thank you and have a Merry Christmas
Roland

Try checking the Agreements section. Participating in the Hardware Program requires signing several agreements before you are able to do anything. I don't know what the acount interface looks like when the agreements are not signed, therefore I'm not sure if this is the cause of your issue or not, but it's worth checking.

All I know is I am lucky enough to have an Azure expert in my organization that fixed this for me. Sadly I cannot tell you how he fixed this but it is possible, He just added another engineer in the last couple of weeks also so there will be a way.

2 Likes

Thanks for the hint. We were never ask to do this but we just tried to send in the agreements possibly missing as a "case". We get a message repeatedly: "Network Failure
Sorry, we had a problem accessing help and support in this panel. Please wait 10 minutes and try again."

I'm not sure we are talking about the same thing. On the screenshot you posted there is a section named "Agreements" in the left menu, just below "Programs". For me it currently looks like this:

I can't remember what exactly it looks like when there are non-signed agreements present, but last time I had to sign them, the interface was pretty clear and didn't cause any confusion. There should be links or buttons which let you read the text of each agreement and confirm the acceptance. (Obviously, the account must have certain permissions to be able to do it.)

We checked and all agreements are in place. We had a video chat with an "Advocate Partner Support Delivery Program" and he confirmed that further support is necessary in this case but deferred us to the MS developer support to open a ticket and this is exactly where we were before :frowning:
We have now three kernel mode driver projects awaiting attestation.
Any hint on how to contact someone who could dive deeper into what went or is going wrong?
Looks like the ticket system works AI driven and semi automated which is probably a good idea but in our case it gets us terribly stuck.

TIA
Roland

Oh boy... Good luck with that. We have been fighting with their support over a driver signing issue for over 9 months already, and still no light at the end of the tunnel. :frowning:

I managed to glean something. If your organization has an Entra ID it appears you cannot simply create another by yourself.

You need to find out who is in charge of the Entra ID (Administrator)_and get them to add you.

At least that is my understanding. The Entra ID Admin for my company ended up being at our parent company.

We have only one Entra id and we can create users with "developer" role. under "Programs->other programs" we see that we can register for the hardware developer program but doing this shows a page telling us that our company is already registered for this and we should contact the "Administrator". Well we do this logged in with our administrator Entra Id. Looking under existing programs we do not se hardware developer. This is driving us crazy as the main administrator should have all the privileges to register for this program.
We would even be willing to pay someone who really knows the system in and out to walk us through this process in a Teams session :wink:

I have just been looking and it seems you are not the only one with this problem.

link1

link2

link3

The only other thing I remember was we had to change our login in ID from

name@ourorganisationname.com

to

name@ourorganisationname.onmicrosoft.com

The onmicrosoft ID is not an email apparently. I just checked this morning and I can still login with Microsoft Authenticator app too.

I just checked again today , and I have exactly the same problem. I already have the correct format administrator id (name@orgname.onmicrosoft.com.) So that doesn't clear the problem. All attempts to get this fixed ended up in support hell or an idiotic ai chatbot that is utterly clueless. Obviously something is wrong, and as the problem is not isolated to my account, Microsoft has broken something and isn't fixing it. I tried burning a support ticket from my VS account, but that team just has no idea what a 'partner portal' is, but would be happy to resolve VS problems.

I would say that something is broken however I had this problem and our IT somehow circumvented it.

I logged in and as you can see we have 4 accounts. The guy with the roles pointed to by the arrow solved the problem described in the OP (basically my account 'vaporized' however he managed to get it back) for me.

Do you need another type of account? (My Account is Admin only). Whoever signs up their organization gets Global Admin access.

After reading this thread I just verified our MS account. For attestation signing we usually log in via https://partner.microsoft.com/dashboard.

I confirm this has to be with our name@orgname.onmicrosoft.com account which MS created for us when we registering many years ago.

So far, so good, all seems to work fine. After logging out, I landed on this web page: https://partner.microsoft.com/en-US which has a red warning box at the top:

Microsoft account (MSA) logins (e.g. @outlook, @google, @yahoo) have been retired from the partner website. In order to access the partner website, you must sign in with a Microsoft Entra ID login (Work/School/Organization). This must be the same login as you use to access Partner Center. If you are trying to sign in with a developer account, please click Partner Center to log in.

This may (or may not) shed some light on the issues described here.

A few years ago I had a problem where attestation signing failed. I spoke to the EV signing certificate supplier and they managed to raise the issue with Microsoft. Took about a month and the problem was fixed. Maybe the EV cert company had more clout.

We also buy a lot of Microsoft licenses and we can get some good contact with Microsoft through the supplier.

It is really annoying to find out you do not have the capability to sign a driver.

| pwilly
January 10 |

  • | - |

After reading this thread I just verified our MS account

Thank you so much for checking this!

For attestation signing we usually log in via https://partner.microsoft.com/dashboard.

So do we!

I confirm this has to be with our name@orgname.onmicrosoft.com account which MS created for us when we registering many years ago.

And this is exactly what we use as login credential.

So far, so good, all seems to work fine. After logging out, I

landed on this web page: https://partner.microsoft.com/en-US which has a red warning box at the top:

Microsoft account (MSA) logins (e.g. @outlook, @google, @yahoo) have been retired from the partner website. In order to access the partner website, you must sign in with a Microsoft Entra ID login (Work/School/Organization). This must be the same login as you use to access Partner Center. If you are trying to sign in with a developer account, please click Partner Center to log in.

This may (or may not) shed some light on the issues described

Well, we never used one of these retired email addresses.
However, inside partner center we are simply unable to „join“ the hardware developer program. Trying this results in a webpage telling us that we are already in this program and should contact our „administrator“ but we are logged in as admin.
Consequently we cannot upload drivers for attestation.
Any attempt to contact a non-AI support failed so far.

After having a bit of time to look for other people with the same problem it seems as if the problem, as Mr Roddy said, is with Microsoft and they don't seem overly interested in fixing it (there are messages in Microsoft boards with the same problem and terrible customer service).

I sincerely feel for you.