Pinned Posts
Forum Widgets
Latest Discussions
End of "Legacy Gold" and the easiest way to change?
The point is that our benefits associated with purchasing the "Legacy Gold" product expire next month, and we're currently offered the following offers in the Partner Center. Is it possible to purchase both packages "Partner Success Expanded Benefits" and "Partner Success Core Benefits" at the same time, thus obtaining a combined total of 50 Microsoft 365 Business Premium licenses? To maintain business continuity, we need approximately 60 Microsoft 365 licenses. We currently have E3, but we're forced to downgrade to Business Premium. This would be a significant one-time cost if we had to purchase these licenses separately, so we'd like to take advantage of the two bundles of offers prepared for us. Is it possible? This will reduce cost demand by x2... I really hope this is possible. If not - what's other options? We need at lease 55 licences for Microsoft 365 but Expanded Package give only 35.
Deployments calculation for Modern Work
Deployments score is calculated by dividing the Active usage values by the Qualified usage values and multiplying by 100 - this result must be greater than or equal to 40 percent, in order for achieving points required for membership qualification, If the results are less than 40 percent, then the customer in question will not meet the basic requirements, and no points are given. As of now, the Active usage value is the number of licenses available on a tenant, and not the actual amount of active users with a valid license assigned. Customers often have licenses with yearly commitment and also have an overage of MS 365 licenses, due to employee hirings and layoffs. This means that the calculated usage percentage if mostly lower than the real life percentages and can never reach 100%. If a customer has a negative development in employee count during the year, it can result in a declining usage score, negatively affecting the points required for the Partners membership eligibility. This even if the actual usage percentage in the customer's end is increasing. We think that the calculation for Deployment score should be changed to reflect the number of acutal active and licensed users (like the Active usage value) , and not be based on the number of licenses available on the tenant.
suggestions for logo/letterbuilder
Dear Microsoft, fellow partners, Partnercenter (benefits section / logo builder at https://partner.microsoft.com/en-us/dashboard/mpn/membership/benefits/logobuilder) offers various documents partners can use to prove their status within the MCAIPP (formerly MPN). These ‘letters’ are similar in setup, but not quite and differ in important aspects which requires these letters to be generated more often that really needed… Legacy letter The legacy competency letter has no enddate (hurray!) MAF letter Valid for 3 months (90 days) Must add 1 sku (?) Requires customer details Requires tender reference Only for non-CSP authorizations/VL ? (MPSA, Enterprise Direct Advisor, EES etc) SPD letter Asks customer details (not required like with MAF) Includes ALL or None of business locations (as opposed to selection in the MAF letter) Only valid for a month (30 days) If we have requests for these letters spread evenly over the year we are required to keep generating a new letter every Q or M depending on what is asked for; while details remain unchanged (except for the date) The Microsoft partnership is renewed once a year, and valid for a year. Any SPD’s attained are also held until next renewal, so there is no apparent need to limit the validity of either proof to a period which isn’t even related to the membership year. Despite that, current properties of the letters ignore these facts leading to unnecessary burden for partners. We have the following suggestions: MAF Remove 90 day period in MAF letter / coterm with membership year* Remove need to add a sku Remove need for adding customer details Remove need for tender reference Optionally also add the CSP authorization based on signed MPA in the MAF as this will be the motion going forward (or would Microsoft prefer to create a separate letter for that…?) SPD: Remove 1 month validity / coterm with membership year* Remove need for customer details Make ‘None’, ‘All’ or selected locations visible on letter *Alternative: list the membership year for the partner, so customers know that between moment of payment for new program year / next years renewal we hold certain authorizations and/or status. (month x until month y next year) With regards to renewal process: could Microsoft please revert to the OLD system, where a partner renews before membership expires? Currently as soon as a partner initiates renewal; the attained SPD’s drop off (also visible in the business profile listing) only to reappear after payment has been received. With regards to the payment process: when do you expect your system to be able to identify the unique combination of Partner ID + Order ID when sending a payment for membership fee; by reading the payment description field? (that would save every partner & their Finance department creating ‘proof of payment’ which is to be uploaded to complete the renewal….) General remarks: Why is it Dan Rippey handing out the solutions partner certified letter, but when we request the Solutions partner congratulatory letter its signed by Nicole Dezen? Kind regards, MartijnPartner experience using Microsoft ECIF Funding for Federal sector?
Looking for some general feedback from ISV, SI, MSP community... We're a mid-sized ISV with some enterprise services capability focused on deployments, cloud migration of both our own and some Microsoft security workloads. We've never used ECIF, but have a few targets where it would be valuable. I'm getting great support from Microsoft program team to onboard to the program and expect to have us activated shortly. Scope-wise, we have a handful of targets and would probably be pleased to execute with them in upcoming year. Question - what are your experiences with ECIF for Fed? What's the "operational lift" to manage a program and capture this benefit? Has this worked well for you? Has it been cumbersome? Any particular areas we should especially focus attention to ensure smooth execution? Any general guidance appreciated.
