Forum Widgets
Latest Discussions
GDAP and the 'Printer Administrator' role
Hello everyone! I see that the 'Printer Administrator' role is available in GDAP. However, we get "401 Error loading your content" messages when trying to access Universal Print in Azure. I checked the Workloads supported by granular delegated admin privileges - Partner Center | Microsoft Learn page but wasn't able to find a section for Universal Print at the moment. I believe a license is required to access this feature, which can't be assigned to an external identity, so I suspect that's our issue. A local tenant admin is able to access the universal print things without any issues. Are we doing something wrong? Can we look forward to seeing broader support for GDAP in the future? Thanks! -jon
Partner Center account deactivated – unable to access Hardware Program dashboard
Hello Microsoft Partner Center Support Team, We are currently unable to access the Microsoft Hardware Developer Dashboard through Partner Center. Below is a summary of the issue and actions we have already taken. --- Purpose We have encountered an access issue when attempting to use the Microsoft Partner Center Hardware Developer Program. The purpose of this message is to request confirmation of our Partner Center account status and reactivation of our Hardware Program registration, or guidance on re-enrolling if required. --- Sequence of Events (Steps to Reproduce) We attempted to access the Microsoft Hardware Developer Dashboard via the following URL: https://partner.microsoft.com/ja-jp/dashboard/Registration/Hardware After signing in to Partner Center, the “Hardware” option appeared in the list of available programs. However, it could not be selected, and the following message was displayed: Hardware Manufacture devices, parts and equipments. Create and manage system and driver submissions. Our records indicate that you have already enrolled into this program but your program registration is deactivated. Subsequently, when attempting to access the Partner Center dashboard, the following error message was displayed: Access restricted – your Partner Center account has been deactivated. --- Additional Information The following details were displayed on the Partner Center dashboard at the time the above error occurred. - Organization name: Sunny Giken Co., Ltd. - Tenant domain: sunnygiken.co.jp - Primary account email: email address removed for privacy reasons - Approx. registration date: August–September 2018 - Error Correlation ID (from screenshot): cac6e9b-5a09-471a-ada7-b8fc0231a78a - Correlation vector: UyZ59dYHRm0KoRkY.3 - Time (UTC): 17 Oct 2025 08:19:26 +00:00 --- Actions Taken - We sent an inquiry email to `email address removed for privacy reasons`, but have not yet received a response. - We also attempted to contact `email address removed for privacy reasons`, but that address appears to have been deactivated (SMTP 550 5.4.1). - The Services Hub support form (supportforbusiness) could not complete submission due to a looping issue. --- Request We kindly request verification of our Partner Center account status and Hardware Program registration. If our organization’s registration has been deactivated, please advise on the procedure to reactivate or re-enroll under our current tenant. --- Thank you very much for your assistance. Best regards, Tetsuya Ozawa Sunny Giken Co., Ltd. email address removed for privacy reasons
Hardware Program registration deactivated and unable to create support case
Our organization completed Partner Verification successfully. However, the Hardware Program still shows "program registration is deactivated". We also cannot access Hardware Dashboard and cannot create a support case because Engage Center returns "No Access". Has anyone experienced this issue or can a Microsoft moderator help route this to the Hardware Program team? Thank you.Feature Request — Programmatic (API) access to Eligible/Ineligible Revenue data
Hi Product Team, We're building an automated backend pipeline to ingest and reconcile our incentive and revenue data across multiple Microsoft programs (MCI/Co-Op), and we've hit a gap we'd like to flag for future roadmap consideration. **Current situation** The Partner Payout API (api.partner.microsoft.com/v1.0/payouts) already gives us solid programmatic access to Earnings and Payments exports, which we use successfully today. However, the Eligible/Ineligible Revenue data available on the Earnings > Revenue page in Partner Center has no equivalent API endpoint — it's currently only accessible via manual UI download. We confirmed this with Commercial Marketplace Support (Service Request #2607220040003782), who kindly clarified that this is a known product limitation rather than a support/configuration issue, and suggested we raise it here directly with the Product Team. **Business impact** Without API access to this dataset, we're forced to rely on a manual, human-driven download step in an otherwise fully automated ingestion pipeline. This creates: - A recurring operational dependency on a person manually exporting and uploading the file on a schedule - A gap in our audit trail, since manual downloads are harder to log and timestamp consistently than API-driven exports - Reconciliation delays between Eligible/Ineligible Revenue and the Earnings/Payments data we already pull automatically via API **Request** We'd like to ask the Product Team to consider extending the existing Payout API (or a comparable endpoint) to support an asynchronous export request for Eligible/Ineligible Revenue data, following the same pattern already used for Earnings and Payments (create export request → poll status → download via secure blob link). Happy to share more detail on our use case if it's helpful for prioritization. Thank you for considering this. Regards, Carlos Rodrigues
Trouble receiving OTP emails from Microsoft Partner Center
Hello! When clicking the Verify Email button in the location below, the primary contact email is not receiving the OTP verification email. I'm on my 6th Partner Center support ticket attempting to determine out why I am not receiving these emails. Partner center support is quick to help me verify the account manually, but I would really like to see the automated system working as intended to help future partners avoid running into this same issue. Could someone help me track down the email address these messages are coming from? Thanks! -jon For reference, the first few tickets I opened under the following workspace/topic, but the assigned engineers say "you picked the wrong topic try again." Workspace: Account Settings Topic: Account verification > E-mail ownership I ask what set of options I should pick to get my ticket routed to the right team, but I haven't located someone that can answer that question either. I've started choosing a random workspace and topic in the hopes that I get lucky. I don't think this strategy is going to work very well, but the partner center support team haven't suggested a better approach and I'm out of ideas. Maybe if I open enough tickets, someone on the partner center support team will notice and help me out.
Microsoft Hardware Dev Center / Partner Center – Four Months Later, I Still Can't Publish a Driver
I'm hoping someone from the Microsoft Hardware Dev Center or Partner Center team sees this. I've been trying since April 2026 to get my account into a working state so I can publish and sign a Windows driver. Instead, I've spent the last four months fighting backend account issues between Entra ID, Partner Center, and the Hardware Dev Center. Current support case: Hardware | Onsite Dental Systems | Incomplete... Tracking ID: #2606060010000492 Over the past several months I have: Worked with multiple Microsoft support engineers. Opened numerous support cases. Followed every instruction provided by Microsoft. Recreated my Entra tenant when instructed. Waited through backend synchronizations and escalations. Re-verified my organization. Recreated applications, permissions, and identities multiple times. Every time one issue appears to be resolved, another backend issue surfaces. At this point, I've spent more time trying to become an approved Microsoft developer than actually developing software. The situation became so drawn out that my original EV code signing certificate expired before Microsoft could get my account working. I had no choice but to purchase another EV code signing certificate, adding hundreds of dollars in unnecessary expense because my account was still blocked by backend provisioning issues. This isn't simply frustrating—it's impacting my business. I'm a small software developer. My customers rely on my software every day, and I cannot complete Microsoft's required driver-signing process because my account remains stuck in a state that only Microsoft appears able to fix. I want to be clear that the support engineers themselves have been courteous and have genuinely tried to help. My frustration is with the platform and the apparent lack of tools available to support when these backend account issues occur. I believe Microsoft should consider: Providing a complete reset option for Hardware Dev Center registrations tied to broken tenants. Better diagnostics instead of generic backend errors. Improving synchronization between Entra ID, Partner Center, and Hardware Dev Center. Giving support engineers the ability to repair account provisioning without weeks of escalation. Publishing documentation for developers who must migrate to a new Entra tenant. If anyone from the Hardware Dev Center or Partner Center team is reading this, I would greatly appreciate someone reviewing Tracking ID #2606060010000492. I've been trying to accomplish what should be a basic task—publish and sign a Windows driver—since April 2026. Four months later, after countless hours, multiple support cases, and even purchasing a replacement EV code signing certificate because the first one expired during this process, I'm still unable to complete it. I truly hope this feedback reaches the appropriate engineering team, because I can't imagine I'm the only developer who has experienced this. Hopefully this process can be improved so other developers don't spend months trying to overcome backend account issues instead of building software.
Partner Center Developer Identity Verification Stuck
My Microsoft Partner Center account is stuck at Legal > Developer > Identity Verification, with the Verification Status consistently showing "Rejected". I have two key questions regarding the identity information submission for AU10TIX verification: 1. Does the contact person name filled in the account need to exactly match the legal name of the account holder? 2. What standard information must be provided to prove the submitter is the legitimate account owner and successfully trigger AU10TIX identity authentication? I have already submitted a support ticket for this issue, but the only reply I received via email simply stated that my submitted information was incorrect, without specifying which fields or content failed the review. I am still unable to identify the exact error in my submission and cannot complete the identity verification process. Could anyone share the correct filling standards for identity verification materials, or advise on how to resolve this persistent rejected status?
Cannot finish registration. Stuck on adding registration number.
Hello, I got stuck, when I added the registration number. It's there, but the "next" button is greyed out as well as the "edit" link. Using this url to start: https://admin.cloud.microsoft/?invType=ResellerRelationship&partnerId=xxxxxxxx&msppId=0#/partners/invitation. Please help :)
