Forum Widgets
Latest Discussions
CSP Transactional TTM Revenue Not Loading for Indirect Reseller - Anyone Else Seeing This?
Hello everyone, We are a Microsoft CSP Indirect Reseller and have been actively transacting through our distributor for more than two years. In the past, including during a Microsoft support review in December 2025, we regularly used the "Partner Global - CSP Transactional TTM Revenue" metric in Partner Center to monitor our CSP performance and eligibility requirements. At that time, the data loaded correctly and was fully visible to our Global Admin account. Recently, the report stopped loading completely. The widget appears, but the CSP Transactional TTM Revenue value never loads. The issue occurs across multiple browsers and devices, so it does not appear to be a local browser or cache problem. The affected report is: Insights > Cloud Product Performance > Subscriptions Reference documentation: https://learn.microsoft.com/en-us/partner-center/insights/analyze-subscriptions-licenses?utm_source=chatgpt.com I opened a support ticket and received a response stating that my account does not have the required permissions and that I should contact my distributor. However, this explanation does not seem consistent because: The same account previously had access to this metric. We can access all other Insights reports normally. Under Account Settings > My Access, access to the relevant workspaces is granted. We are an active CSP Indirect Reseller with paying customers and active subscriptions. My questions are: Has Microsoft changed the visibility or permission model for CSP Transactional TTM Revenue recently? Is this metric still available for CSP Indirect Resellers, or is it now restricted to certain partner types? Is anyone else experiencing the same issue where the widget appears but never loads the revenue data? Has anyone received official communication regarding changes to this report? Any feedback or confirmation from other CSP partners would be greatly appreciated. Thank you.4Views0likes0CommentsPartner Collaboration – Copilot AI Readiness Sprint (MPN ID: 7110817)
Hello Microsoft Partner Community, We’re seeing increasing demand from clients exploring Microsoft 365 Copilot — and a consistent gap in readiness across licensing, data, governance, and security. ArcSecureAI (MPN ID: 7110817) is offering a virtual Copilot AI Readiness Sprint designed to support partners working with SMBs, nonprofits, and organizations preparing for adoption. What the sprint includes: • Readiness assessment (licensing, data, governance, workflows) • Security and Zero Trust alignment review • Identification of automation opportunities (Power Automate + Copilot Studio) • Scored readiness report (0–100) • Practical 30–60–90 day adoption roadmap Partner collaboration options: • White-label delivery • Co-delivery with CSPs and MSPs • Fast turnaround (typically 48–72 hours) • Microsoft-aligned approach Goal: Help partners start the Copilot conversation with structure, deliver immediate value, and position follow-on services. If you’re currently working with clients evaluating Copilot, I’d be open to connecting and exploring collaboration opportunities. – Sreita Wheeler ArcSecureAI LLC MPN ID: 711081725Views1like0CommentsTax ID Update -- no support
Hi there. I cannot add my TAX ID in the account settings workspace. Or any other place seemingly possible according to the Partner Center AI Assistant help feature, Google articles, and so on. I have followed various instructions for updating my TAX ID but none resemble precisely what I am seeing. I have been trying to resolve this myself for weeks now. I have two support tickets in with MS, have followed them each up in the tickets, all to no avail. I am part of the MAICPP, a CSP etc., and have been for a while. As you can see, my bill information is not linked which may be why I cannot edit/add the TAX ID according to the myriad instructions I've found. BOTTOM LINE: I do not know how to obtain support assistance from MS. Anyone have any suggestions? Thanks.SolvedacarstensMay 15, 2026Copper Contributor110Views0likes1CommentPartner Center Enrollment Blocked – Trust Code 715-123160 – Requesting Manual Review
Hello Microsoft Partner Community Team, We are attempting to enroll our company in the Microsoft AI Cloud Indirect Seller Program, but our registration is being blocked by the automated trust verification system. We are a legitimate, legally registered business operating in the cloud connectivity industry. Our DUNS number and all company information entered during enrollment are accurate and match our official government records. Error details: Reference Number: 715-123160 Transaction ID: 0e136d6b-9164-41c3-be26-9b301c9aac24 Correlation ID: e827ab99-6dc9-4901-a464-cff43d00f5c7 Due to this block, our Partner Center account has no active workspaces, which means we are completely unable to create a support ticket through the standard Partner Center portal. We have also tried the partner.microsoft.com/support page, but it redirects us back to Partner Center — creating a loop with no resolution. We are kindly requesting: Escalation to the Partner Center Vetting / Trust & Safety team for manual review A reset or unblock of our enrollment so we can complete registration Guidance on any documentation required (business registration, address proof, domain ownership, etc.) — we are ready to provide everything immediately for email contact, please contact the email address we leave on the request (format as: email address removed for privacy reasons) Thank you in advance for your assistance.healtheworldplzMay 04, 2026Copper Contributor46Views0likes0CommentsCSP Account suspended without notification, no explanation given
Hello Microsoft Community, I'm hoping someone here has experienced something similar and can point me in the right direction. I have been a Microsoft Partner since 2019. This past January I renewed my Partner Success Core Benefits pack. A couple of weeks ago I noticed I had lost access to all my benefits. I opened a support case, and after going back and forth I still have no resolution. The only explanation I've received is a reference to section 4.b of the Microsoft AI Cloud Partner Program Agreement, which states that either party can terminate the relationship with 30 days' notice and without providing a reason. No notification was ever sent to me. No 30-day notice. I simply woke up one day with no access. At one point I was told I could re-enroll under a new tenant. I tried this, and it didn't work. When I followed up, the support team went back to citing section 4.b and closed the door again. I understand I'm a small partner in Microsoft's ecosystem, but I've invested years building my business around this partnership, renewed my benefits in good faith just a few months ago, and I would love to find a constructive way forward. My questions for the community: 1. **Is there a formal escalation path** beyond standard Partner Center support cases? 2. **Has anyone successfully re-enrolled** after a suspension of this kind, and what was the process? Any guidance, shared experience, or contacts would be enormously appreciated. I am not looking to complain, I just want to understand my options and get back to serving my customers. Thank you in advance.bjclsApr 16, 2026Brass Contributor105Views0likes0CommentsICYMI: Turn upcoming virtualization licensing changes into a growth opportunity
Seize the market shift driven by recent virtualization licensing changes by accelerating the move from Service Provider License Agreement (SPLA)-based licensing to a Cloud Solution Provider (CSP) model. Read more hereJillArmourMicrosoftApr 16, 2026Community Manager109Views0likes0CommentsCSP account suspended without notice, no explanation given. What are my options?
Hi everyone, I'm hoping someone in the community or perhaps someone from Microsoft can help me understand what happened and what I can do next. I've been a Microsoft partner since 2019, and last January I renewed my Partner Success Core Benefits program. A few months later, I discovered my CSP account had been suspended with no prior notification whatsoever. I opened a support ticket, and the response I received cited section 4.b of the Microsoft AI Cloud Program Agreement, essentially stating that Microsoft can terminate a partner relationship with 30 days' notice and is not required to provide a reason. I understand this is contractually possible but I received no notice, and no explanation. After re-opening the case multiple times, I was told to enroll into a new tenant with a new enrollment. I attempted this, but it did not work. When I followed up, I received copy-paste responses directing me back to the same steps. To summarize where I am right now: Partner since 2019, with renewed subscriptions as recently as January Account suspended and no advance notice received No explanation provided, citing section 4.b of the agreement New tenant enrollment suggested but unsuccessful Support has been non-responsive beyond templated replies I'm not here to argue, I accept that Microsoft has the right to make decisions about its partner ecosystem. What I'm asking for is basic transparency: did I do something wrong? If there was a compliance issue, a policy violation, or any other reason for the suspension, I would genuinely like to know so I can understand and, if possible, address it. I also have some practical questions the community may be able to help with: Is there a formal appeal or review process for suspended partner accounts? Is new enrollment genuinely possible after a termination under 4.b, and if so, what are the correct steps? Has anyone else experienced this and found a way to resolve it constructively? Is there an escalation path beyond the standard support ticket process? I know I'm a small partner and this is likely a minor matter from Microsoft's perspective. But for a small business that has invested years in this program and renewed in good faith just months ago, this situation has had a real impact. A clear explanation, even a difficult one would go a long way. Any guidance, shared experiences, or pointers to the right escalation channel would be greatly appreciated. Thank you.bjclsApr 16, 2026Brass Contributor288Views0likes3CommentsUnified for Partners (UfP) - Pricing
We are a Microsoft Direct CSP currently purchasing Premier Support for Partners (PSfP). With Premier support we are allowed 30 cases/year and after that you have to pay approx. $650/case. We do a good job of handling issues on our own and only open tickets on our customers behalf as a last resort. We will have approx. 20 cases this year and won't need to purchase any additional. Under (UfP), based on the datasheet released we will qualify for a 40% discount on the Licensing & Azure rates. With the 40% discount our annual costs will increase 8x what we are currently paying. Our cost/case will go up to $12,725(1,800% increase) Is Microsoft trying to put their existing CSPs out of business with this pricing model? We have been driving new business and been a model partner. We have already had to deal with the complications of all of the risk and additional issues brought on by NCE and now we are going to be price gouged for support. The marketing materials are trying to make this look like a benefit to us when in fact it is the complete opposite. Will there be exceptions to this new pricing model? It made a lot more sense to charge CSPs per case they open above the 30 allowed. Why wouldn't Microsoft just increase the cost of the additional cases? This would make CSPs double think about opening a case that they may be able to solve on their own. (UfP) is going to punish the good CSPs by spreading the cost of companies abusing the system across the board. We would love to have the opportunity to express our concerns with a Microsoft representative in the CSP program. We have already made our PDM and Success Manager aware of the impact that this will have.SolvedNickGApr 14, 2026Brass Contributor341Views3likes7CommentsDirect Bill Partner Status - Terminated
Hello, I'm writing here after four months of unresolved escalation through every standard support channel, and after reading the recent threads from ShayD , swathen , and ElDani . Our case appears to belong to the same family of issues, and I'm hoping raising it publicly will help both reach the correct internal Microsoft team and establish the broader pattern that seems to be affecting multiple partners across different markets. Who we are We are a longstanding Microsoft CSP partner based in Mongolia. We are the only Direct Bill CSP partner in the country, one of our market's top CSPs overall, and a multi-time Microsoft Country Partner of the Year. We service a large active customer base across enterprise, public sector, and SMB segments. What happened February 2, 2026: Original support case opened regarding a billing report discrepancy that surfaced in our Partner Center data. March 31, 2026: Microsoft formally acknowledged, in writing, in case #2602020010000623, that the discrepancy was caused by a Microsoft-side reporting error — not by any action or non-compliance on our part. April 1, 2026 — one day after the written acknowledgment of fault: Our Direct Bill Partner status was revoked by the system, and our Partner Center management capabilities were disabled the same day. We can no longer provision, modify, or service customer subscriptions. Since April 1: We have opened five separate support cases attempting to resolve the revocation. Each has been force-closed with instructions to file a new one. None has produced a named owner, a timeline, or a resolution path. Responses have consistently been variations of "under review" or "identifying the correct team." A TP&D ticket filed on the recommendation of our ASfP support manager was closed as out-of-scope. Our ASfP manager has confirmed that they cannot identify the correct internal escalation path, and mentioned that similar cases have been observed in other markets recently. Current impact A large base of end customers — including public sector and enterprise accounts — can no longer be properly serviced through their established CSP relationship. As the only Direct Bill CSP, our incapacitation effectively means Microsoft currently has no functioning Direct Bill CSP coverage in an entire country. Any customer requiring services through this channel has no path to receive them at the moment. Customer impact is accelerating each week the situation persists, and the reputational consequences are extending into the local market more broadly. What we're asking for Escalation of the above tickets to the appropriate CSP Accounts & Enrollment team, or to whichever internal Microsoft team owns erroneous Direct Bill revocations arising from billing report errors. Reinstatement of our Direct Bill Partner status, given that Microsoft has already formally acknowledged in writing that the root cause was an internal reporting error. Assignment of a named owner with authority to drive this to closure — not another ticket transfer into a queue. A broader note for Microsoft and the community In the past several weeks, multiple partners have posted here about erroneous or unexplained Direct Bill terminations. ShayD 's thread (resolved after Microsoft formally acknowledged the termination notice was sent in error), @swathen's thread (revenue classification / visibility gap causing an eligibility review failure despite provable revenue), and ElDani 's thread (Direct Bill account suddenly suspended April 1, 2026 — same date as ours) all share meaningful structural similarities with our case. Our situation makes at least the fourth public report of a similar pattern within roughly the last two months. I'm raising it here not to escalate emotionally, but because it genuinely seems worth Microsoft's internal attention that this may be a systemic issue in the billing classification or partner status pipeline, rather than a set of unrelated isolated cases. If anyone at Microsoft is tracking this pattern internally, our case is one more data point and we'd welcome being part of whatever review is happening. Any Microsoft employee who can help route this to the right team, or any partners who have successfully navigated a similar situation, please reach out. Full case documentation — including Microsoft's written acknowledgment, the complete chronological case history, and supporting materials — is available on request through direct message. Thank you for reading.AmarbatApr 14, 2026Copper Contributor97Views1like0Comments
Tags
- CSP180 Topics
- Partner question110 Topics
- direct84 Topics
- Indirect reseller76 Topics
- Indirect66 Topics
- Indirect Provider47 Topics
- Pricing & Licensing2 Topics
- CSP Hoster1 Topic
- support1 Topic