Forum Widgets
Latest Discussions
new partner tenant - price sheet API calls don't work
I work for a CSP direct partner with multiple tenants. We're currently setting up a Netherlands tenant, and I can't manage to make calls to retrieve price sheets. I think the underlying issue is that this tenant is missing the enterprise app for "Microsoft Partner" (ID 4990cffe-04e8-4e8b-808a-1175604b879f), so I can't add a permission for it to my app registration. Any clue how I can add it? Do I have to open a support ticket or can I do it myself? It's present in our other tenants (US, Ireland, etc.). Price sheet API docs: https://learn.microsoft.com/en-us/partner-center/developer/get-a-price-sheetEmployment Verification appeal (Resolve) panel does not render upload option
Partner ID: 7001033 Company: Conligo Services B.V. Account: Microsoft AI Cloud Partner Program, Developer track Issue: Legal Business Profile Verification is stuck at Employment Verification (status: Rejected / Pending Partner Action). Following the official appeal process (Legal Info → Verification Summary → Resolve), the panel that opens does not match Microsoft's own documented behavior. Expected behavior (per Microsoft's official documentation, "Submit a verification appeal in Partner Center," step 6): the Resolve panel should show a "Select document type" dropdown, a drag-and-drop file upload field, and an optional comments field. Actual behavior: the panel only displays a static message — "Your document was submitted successfully. Review can take up to 5 business days." — with no document type selector, no upload field, and no functional control of any kind. Troubleshooting already performed: Reproduced in multiple browsers (including a fresh anonymous/private session, tested independently, ~30 minutes apart) Reproduced after waiting to rule out temporary state/cache issues Confirmed the Verification Started, Email Verification, and Identity Verification steps all show as passed (green checkmark); only Employment Verification is affected Confirmed via KvK (Dutch Chamber of Commerce) extracts that I am the authorized representative (director of Ubertas Holding B.V., which is the sole director of Conligo Services B.V.) Documents ready to submit once the upload field is functional: KvK extract, Conligo Services B.V. (KvK 77027965) KvK extract, Ubertas Holding B.V. (KvK 76957292) Domain ownership documentation for conligo.nl (WHOIS/registrar confirmation) Request: please either fix the rendering issue on my account, or provide an alternative channel to submit the above documents for the Employment Verification appeal.
Verification docs resubmitted as requested — 9 business days, zero response — 2608140040001875
MPN Account ID: 7136847 Tracking ID: 2608140040001875 Timeline: Initial rejection on Aug 8. Case reopened, Vetting Operations requested additional business registration documents (address change filing + updated GST registration reflecting our current registered address). We submitted these on Aug 14, the same day they were requested. Your team's message committed to a follow-up within 2-3 business days — it's now been over a week with no acknowledgment of receipt or status update on the ticket. Could someone from Vetting Operations confirm receipt of the documents and the current review status? Happy to share any additional verification details by DM if that helps move this along. Thanks in advance. AshishGDAP 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
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
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?
