Program Tools (non OSU) Ideas/Suggestions

a {text-decoration: none;color: #464feb;}tr th, tr td {border: 1px solid #e6e6e6;}tr th {background-color: #f5f5f5;}Request: Quarterly Graphical View of Upcoming EA / CSP Tenant Renewals in ASPXImpact: Provide at‑a‑glance visibility of upcoming renewals by quarterSupport early action planning for retention, upsell, and migration conversationsReduce reactively applying filters on the renewals to view the opportunity

In the absence of an FRP dashboard, partners currently lack a centralized way to track Copilot Chat Monthly Active Users (MAU) growth on a month‑over‑month basis across individual tenants in ASPX.Partners actively invest in driving Copilot adoption through multiple engagements such as MCI sessions and trainings. However, there is no mechanism to track usage from the start of these engagements and monitor sustained growth over time.Introducing tenant‑level, month‑wise Copilot MAU tracking would enable partners to measure impact, optimize engagement strategies, and demonstrate business value more effectively

Distributors have customers assigned to resellers via CSP licensing and sometimes those customers also have EA agreements. The Copilot Whitespace is based on all licenses to that customer regardless of purchasing vehicle. It is requested that when we filter it based on CSP, that the whitespace totals also adjust. The tier 2 reseller feels that that may not have an opportunity to fill all of the whitespace associated with the customer as they cannot have an effect on the EA licenses. being able to filter the whitespace based on vehicle will give the tier 2 reseller a true view of their opportunity. 

It would be great to be able to filter on the Tier 2 reseller name in the ASPX UI

Its becoming more apparent that in many cases the purview and Copilot conversations are intertwined. Is there a way to identify the tenants that have whitespace opportunities that overlap in those to workloads? Otherwise downloading and running an agent may be the solution??

Idea This idea is a dedicated partner-facing session that introduces the latest ASPX dashboard updates and upcoming roadmap. Partners can easily catch up on recent enhancements and understand future capabilities so that they can actively and effectively leverage ASPX in their customer engagements. As an option, we can also open the session to a broader partner audience, including Non‑FRP partners. In recent sessions in Japan that included Non‑FRP partners, a PSM introduced the ASPX dashboard. Most Non‑FRP partners were not aware of the dashboard, and after learning about it during the session, they showed strong interest. Business Problem / Pain Point Many partners are not fully aware of new ASPX functionalities or roadmap changes, which limits their ability to use the dashboard strategically. Without regular updates, partners miss opportunities to improve their planning, reporting, and execution based on the most current data and insights.   Expected Impact A structured update session will significantly improve partner productivity by reducing time spent searching for information, eliminating guesswork, and enabling more data-driven conversations with customers. It will also reduce manual back-and-forth clarification and improve the quality of partner execution using ASPX.

One of the distributors that is integrating ASPX with the APIs has suggested that along with the Teir 2 reseller name that we should include the Partner ID or the tier 2 reseller MPN ID in the feed. This will help with their integration into their internal tools and marketplaces.

This feature adds an At Risk column to ASPX Copilot Opportunities. Partners can quickly identify tenants with very low paid Copilot usage so that they can take proactive actions engagement, enablement, adoption support to prevent Copilot license churn. The experience is similar to the existing At Risk Tenants column in ASPX Secure Productivity. Partners currently lack visibility into Copilot adoption risk within Copilot Opportunities. Low usage tenants are often discovered too late, after churn discussions have already started. Without an at risk signal, partners must rely on manual analysis or assumptions, which delays intervention and reduces retention.

Currently Partners are only able to view opportunity details in ASPX for customers they have registered CPOR on. This is great where relationships exist already, however there are many times when account teams present new customers with no link to the Partner.  It would be beneficial for Partners to have a holistic picture of the customer landscape in those initial conversations to help shape an outcome that will have a higher chance of resonating with the customer and therefore landing successfully. This also reduces the amount of time expended given a Partner would likely have to engage the account team and or customer direct to get the required information.  Ultimately this would reduce lead conversion times significantly, reducing effort across the board, and likely see greater satisfaction for all involved.  While it was raised by 1 Partner, this would benefit all Partners globally. Given the potential positive impact, releasing this capability sooner rather than later would be highly beneficial.   

When we include the Teir 2 reseller name into the ASPX data feeds, is there a way to include the Teir 2 resellers MPNID along with the name. It can prove to be a good validation point for the Distributors to connect the tenant usage data.