Artifact Signing
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Azure asks me for domain invoices and registry confirmation records second time
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 91%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Arthur L
45
Reputation points
The problem is Microsoft has asked me for the same info again. The first time they asked, I sent my godaddy domain purchase receipt under my name, not my company. They asked me after to provide a website showing name, address, contact information, and location of organization and I did that, but now they are asking me to provide domain purchase invoices or registry confirmation records again.
Artifact Signing
{count} vote
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 85%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Richard S 0 Reputation points2024-08-02T17:35:26.7566667+00:00 We are having the same issue. Why is Microsoft Azure choosing to use an inconsistent and less secure method for verifying domain ownership than asking for a TXT DNS record to be added like usual?
Asking for these details above, I can provide an 11 month old purchase receipt for a domain I've since sold on and Azure will continue to allow me to sign applications for that domain!
Just let us add TXT DNS domain records, which prove current ownership and access, and is consistent with the rest of Azure
-
Sign in to comment
Sign in to answer