Microsoft’s September 8 Partner Center announcement signals a meaningful shift in how partners should think about AI Business Solutions & Security Partner eXperience, better known as ASPX. Rather than positioning ASPX only as a reporting environment, Microsoft is now describing it as an action engine for identifying the customers most likely to adopt, expand, and benefit from Microsoft 365 Copilot and related AI workloads.
For Cloud Solution Provider distributors, indirect resellers, direct-bill partners, scale solution providers, and systems integrators, the important point is not simply that new dashboards exist. The bigger change is that Microsoft is trying to turn customer signals into prioritized partner motions: who is ready to buy, who is blocked, who is already using Copilot in ways that indicate expansion potential, and which tenants may be ready for the next wave of AI services.
What changed
ASPX is being expanded around five FY27 priorities: free-to-paid conversion, Microsoft 365 E7 targeting, Microsoft Copilot Cowork usage, frontier account targeting, and API v1.5. Together, these updates are intended to move partners from broad account planning toward more evidence-based opportunity identification.
The announcement frames ASPX as a place where partners can uncover signals tied to readiness and adoption barriers. That is a practical distinction. Traditional partner reporting often answers what happened last month or quarter. The updated ASPX direction is more focused on what action a partner should take next.
This matters because Copilot growth is not just a licensing motion. Customers may need readiness work, security posture improvements, adoption planning, change management, data governance, or integration support before a paid deployment scales. If ASPX can help partners identify those situations earlier, it becomes a planning tool for services as well as licensing.
Free-to-paid: finding demand that already exists
One of the clearest partner use cases is free-to-paid conversion. Microsoft says ASPX will surface high-intent signals such as license requests and users reaching free usage limits. These signals are useful because they reduce guesswork.
Instead of starting every Copilot conversation from a generic campaign list, partners can prioritize tenants where users have already shown interest. That changes the sales conversation. The partner can move from “Would you like to learn about Copilot?” to “We see signs that users in your organization are exploring Copilot; let’s review whether a paid deployment makes sense and what controls should be in place.”
For partners, this can improve conversion efficiency. For customers, it can create a more relevant conversation around demand, governance, and readiness.
Microsoft 365 E7 targeting and expansion planning
The announcement also highlights Microsoft 365 E7 targeting. Microsoft’s goal is to help partners identify customers most likely to expand by using telemetry, usage, and licensing data rather than broad account lists.
Whether a customer is ready for a higher-value Microsoft 365 motion depends on more than company size. Signals such as active service usage, existing licensing footprint, security needs, compliance drivers, and AI adoption intent can indicate whether the customer is a realistic candidate. ASPX is being positioned to bring those signals into a more usable partner workflow.
Partners should treat this as an opportunity to tighten account segmentation. A large installed base is not automatically a high-probability expansion target. Conversely, a smaller customer with strong usage patterns and clear security or productivity needs may be a better near-term opportunity.
Copilot Cowork usage as an adoption signal
Microsoft also calls out Microsoft Copilot Cowork usage. The partner implication is that usage data can help identify where customers are already seeing value. This can support two motions: adoption support and expansion.
If usage is rising, partners can engage customers about what is working, which departments are benefiting, and where additional licensing or services may be justified. If usage is uneven, partners can diagnose blockers such as training gaps, unclear use cases, data access concerns, or lack of champions.
The practical advisory for partners is to avoid treating usage as a vanity metric. Usage should lead to a next action: a workshop, adoption campaign, executive review, security assessment, or expansion proposal.
Frontier account targeting
Frontier account targeting is aimed at identifying tenants ready for upcoming AI workloads. Microsoft’s announcement does not provide deep technical detail in the Partner Center notice, but the direction is clear: ASPX will help partners spot customers positioned for the next phase of AI adoption.
For partner planning, these accounts deserve a different engagement model. They may be good candidates for roadmap briefings, pilot design, data readiness assessments, or early workload discovery. The key is to match the maturity of the customer to the maturity of the offer. Pushing every customer into frontier workloads too early can create friction; identifying the right early candidates can create differentiated partner value.
API v1.5 and operational integration
The API update may be one of the most important items for partners with mature sales operations. Microsoft says API v1.5 reduces the integration surface from more than 80 endpoints to four, adds streaming, and improves documentation.
That simplification matters. Partner organizations often need ASPX data inside CRM systems, BI platforms, account planning tools, and managed service workflows. If the API is easier to integrate and maintain, partners can operationalize these signals instead of requiring sellers to check another portal manually.
The best outcome is not another dashboard. The best outcome is a prioritized task, account flag, campaign list, or customer success workflow that appears where the partner team already works.
Recommended partner actions
Partners should start by signing in to ASPX and reviewing the Copilot Opportunities tab. Focus first on whether the surfaced opportunities align with current account plans, pipeline, and customer success motions.
Next, map each signal type to a specific play. For example, free usage limits may trigger a licensing conversation, while low or uneven usage may trigger an adoption engagement. E7 targeting may route to a security and productivity assessment, while frontier signals may route to an innovation workshop.
Sales operations teams should evaluate the API v1.5 changes and decide whether ASPX data should be pulled into CRM, reporting, or campaign systems. The simpler endpoint model may reduce the cost of maintaining an integration and make it easier to distribute signals to the right teams.
Finally, partners should train sellers and customer success managers on how to interpret the signals. A signal is not the same as a closed opportunity. It is a prompt for a better-informed conversation.
Bottom line
ASPX is becoming more action-oriented, with Microsoft using partner-accessible signals to support Copilot conversion, expansion, adoption, and future AI workload targeting. Partners that turn those signals into repeatable plays will be better positioned than those that treat ASPX as a passive reporting destination.