Partner 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: 7110817
Unified for Partners (UfP)
Hello! A few months ago at Microsoft Ignite, Dan Rippey shared an update on The Future of Partner Support - Customer + Partner + Microsoft. Dan brought 'Unified for Partners' center stage and mentioned that Microsoft is going into listening mode and taking partner feedback. It's easy to share feedback with Microsoft by visiting booths at Ignite. What are some ways partners can share feedback with Dan and others at Microsoft year round? For reference, we have a signed NDA with Microsoft if that helps! My first thought are the two community calls that were running for most of 2025. They were the CSP Technical Training Series and Microsoft Partner Community Q&A Call. However, I don't see any upcoming events scheduled... Thanks! -jon
Direct 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.
Direct Bill - Suspended
Hello Today our CSP Direct account was suddenly suspended, and unfortunately we still do not know the reason. We opened a support ticket immediately and received a phone call shortly afterwards informing us that the case had been escalated to the Accounts and Enrollment team. However, since then, we have not received any further updates, nor any reply to our follow-up emails. At the moment, existing subscriptions are still being renewed automatically, which is a relief, but we are currently unable to perform any management actions on the existing subscriptions. I am becoming increasingly concerned that this may be one of the cases I have seen mentioned here by other partners. We currently manage hundreds of customers and thousands of subscriptions, all of which are now effectively without commercial management. Has anyone gone through a similar situation and can offer any advice, guidance, or suggestions on how to escalate the case and speed up the resolution process? Any help would be greatly appreciated. Thanks in advance. Daniel
URGENT: CSP Direct Bill Termination due to Revenue Discrepancy / Visibility Gap Support Exhausted
We’re currently working through a CSP Direct Bill eligibility review and have run into a discrepancy that we’re hoping other partners may have experience with. Our organization has been operating under CSP Direct Bill and, based on Partner Center indicators and prior guidance from Microsoft, we believed we were meeting the ~$1M TTM revenue requirement. However, we were recently informed by Microsoft that our Direct Bill revenue is being calculated at approximately $892K, below the threshold. The key issue appears to be related to revenue classification: Microsoft indicated that some of our revenue may be attributed to CSP Indirect Reseller (IR), even though we do not actively transact through a distributor. All licensing is billed directly by Microsoft, and we can provide invoices to support this. We’ve also been told that when tenants are associated with both Direct Bill and Indirect models, the 12-month revenue breakdown is not visible in Partner Center. Microsoft has acknowledged that this visibility gap exists and that partners cannot currently see the same classification used internally. Our case is currently under review with Microsoft, but we’re trying to better understand: Has anyone encountered a situation where tenants were classified as indirect without actively selling through a distributor? Are there any reliable ways to identify which customers or subscriptions may be tagged as indirect? Has anyone successfully reconciled or corrected this type of revenue classification issue? Any insights or similar experiences would be greatly appreciated, especially if you’ve navigated this during a Direct Bill eligibility review. Thanks in advance.
Partner Support Services Designation Public Preview Deck + Nomination Form
There is a new Partner Support Services Designation in Public Preview. Partners who earn a Support Services designation will be given access to Microsoft tools and resources to enhance their support capabilities. Badging for the designation will help partners differentiate their organizations with customers and in the Microsoft commercial marketplace. Read more here.Character limited for Partner Support Ticket notes
When updating a partner center support ticket from the Partner Center (https://partner.microsoft.com/dashboard/v2/support/servicerequests) However, the textbox for adding a new note from the portal has a max length of 80 characters. Has anyone else noticed this? I shared this observation with the partner center support team a while ago and learned that the portal is working as intended. The web portal should only be used for adding short notes. For longer notes, partners should update the ticket via email. I hoped my feedback might reach someone that could make this improvement to the partner experience, but it's taking longer than expected. Has anyone else noticed this issue, or am I the only partner that finds this behavior less than ideal? On more than one occasion I have modified the HTML using the browser dev tools by changing the maxlength="80" to "maxlength="800" and didn't have any trouble adding the longer note. Has anyone else run into this challenge and used the a workaround like the one I used?
