Forum Widgets
Latest Discussions
Help needed to enroll in the Microsoft Edge Program
I've been really struggling to find help on enrolling in the Microsoft Edge program. I am getting the error message "This account is not registered with Microsoft Edge program on Partner Center" I've tried a few things that has not worked. The error message said to work with my email administrator. However, my workspace's admin also gets the same error. So it does not seem like the administrator is able to do this. I tried opening a support ticket. To open a support ticket I had to choose a topic but there's no topic for this. I ended up choosing something an area under Microsoft AI Cloud Partner Program. The support closed my ticket as it's not part of their area. Where should I go to get help on registering with Partner Center?
PartnerCenter Rest Api WebHooks
Hi everyone, I’m using the webhooks of partnercenter rest api, but there is a problem compared to what described in the technical specifications. In the documentation https://learn.microsoft.com/en-us/partner-center/developer/partner-center-webhook-events#createtransfer-event it is specified that the ResourceUri consists of "{baseURL}/webhooks/v{version}/customers/{customer_id}/transfers/{transfer_id}" but this is not the case! The notifications come with a ResourceUri "{baseURL}/webhooks/v{version}/customers/{customer_id}" and this creates a problem as it is not possible to trace the TrasferId in a safe way. Please can someone fix it?
Eligibility criterion of Copilot funding is not clear e.g. validated Copilot practice and offer
We are trying to raise funding as per eligibility defined in Microsoft Commerce Partners Incentives Guide. But we are not able to understand eligibility criterion: Q1.Partners with a Modern Work -->Question-Does that mean Modern work Solution Designation? Q2. or Business Applications specialization --> Question - Does that mean, we can chase any specialization out of 8 options? Q3. and validated Copilot practice and offer --> Question-not sure what does this mean? How to achieve this? Kindly try to be descriptive with details. Thanks.
Question about the new Partner Benefits options
We are a small ISV that has been in the Partner program (Now CSP) almost since it's beginning. For most of the time we have been in the program we have maintained our eligibility by having our software certified. But then Microsoft changed the requirements to be mostly revenue based and we were no longer able to maintain our Gold level (or silver level). We were still able to purchase the benefits that we use as a legacy Gold partner. But now it appears that Microsoft is getting rid of this next year. So I'm wondering what our best option or options are going forward. I've seen several emails about a new certification process as well as some new options for benefits. Based on our renewal date it appears that we will have to transition to the new benefits options. With the legacy Gold partner benefits, we currently have a monthly Azure benefit of $100 plus I believe some kind of reduced licensing cost for our Azure VMs related to our MSDN subscription which comes from the legacy Gold partner benefits. I found information about the new offerings here https://partner.microsoft.com/en-US/partnership/compare-programs I've reviewed the different offerings and it looks like the Partner Success Core Benefits and either the ISV Success Core Package or the ISV Success Expanded Package would be appropriate So that leads to my two questions: First, do we have to select and purchase both a benefits package and a software offering? Second, with our current legacy Gold partner benefits we'd annually renew our Azure benefits from the MPN site and that would flow directly to our Azure subscription. Will this stay the same with the new benefits? Thanks NickHow can I get private offer info base on subscription Id？
When a customer places an order using a private offer link and the Landing Page is configured, I can obtain the current SubscriptionId. However, when I use thissubscriptionId to get the subscription detail (https://marketplaceapi.microsoft.com/api/saas/subscriptions/{subscriptionId}?api-version=2018-08-31), the returned offerId is the public offerId, NOT the private offerId. How can I obtain the private offerId? Or where did I go wrong? In fact, I want to obtain the price information set for the private offer using the private offerId. Thank you! { "id": "test", "publisherId": "publisherId", "offerId": "public_offer_id", "name": "name", "saasSubscriptionStatus": "Subscribed", "beneficiary": { "emailId": "", "objectId": "", "tenantId": "", "puid": "" }, "purchaser": { "emailId": "", "objectId": "", "tenantId": "", "puid": "" }, "planId": "planId", "term": { "startDate": "2024-07-18T00:00:00Z", "endDate": "2025-07-17T00:00:00Z", "termUnit": "P1Y" }, "autoRenew": true, "isTest": false, "isFreeTrial": false, "allowedCustomerOperations": [ "Delete", "Read", "Update" ], "sandboxType": "None", "created": "2024-07-18", "lastModified": "0001-01-01T00:00:00", "quantity": 4, "sessionMode": "None" }PSA: Verified Publisher (Wrong) Assumptions
First and foremost, thank you, Nilesh Vishwakarma and Deepack, for sharing your internal knowledge to dispel the unnecessarily confusing topic of App Verified Publisher. I'll dive into the details of the issues, the confusion, and what I gathered during a few meetings with Microsoft Support. But first, for those seeking the simple TLDR guidance (specifically for the Verified MPN): The organization/tenant the App is under must have its own Partner Account; you can't come in with your own MPN for your clients; it needs to be their (your clients') MPN Account. Even if you created the App (the App Owner), you need some sort of Global Admin type access, and it seems like you also need some access in the associated MPN account. VERY IMPORTANT: Even if you can see and click on the Verified Publisher link to add an MPN ID, any errors you encounter are likely due to lacking rights in one or both systems. VERY IMPORTANT: The Microsoft documentation for troubleshooting this issue may lead you astray. After several days of troubleshooting on my own—reading, researching, and even involving Microsoft Support—the issue was finally resolved when my client created an MPN account, logged into Entra, clicked the Verify link, and entered their MPN ID. The takeaway here? Assume you're at the mercy of the zero trust hammer, and for something as simple as single sign-on authentication, your clients must become Microsoft Partners. For those not interested in the juicy details or listening to a grumpy gray beard rant, you are hereby released; the above are the main points to remember when applying a Verified Publisher to your App. For the rest of you, read on, and hopefully, you'll pick up more details and maybe even find it entertaining... First, if you are creating a simple App for SSO (work/school) for use on your client's website, you need to create the App on the tenant that holds the AD/Entra accounts. This makes sense. Furthermore, a publisher is required to be on the hook for and prove the validity of the App, visible to users during the consent. This also makes sense. However, what doesn't make sense is that the App Owner cannot assign the MPN ID, and even more so, anyone who is creating that App for their client needs also to have access to their client's MPN Account, and, for that matter, that the client should even need that MPN Account. Let's start with an extreme example... I'm building a website for a construction company that doesn't have an IT team. Because they have AD/Entra and I'm a loyal "Microsoft Partner" (see what I did there), we decided to go with Azure and Entra. First, I need to explain the access I think I need to the client (who is not technical). I'm on my way, creating the App and website, and I get to this Verified Publisher thing. Okay, no problem... I can click on this link to add my MPN ID. Nope, that's the first error. After finally figuring out that they need to become a Microsoft Partner, you help walk your (again, non-technical) client through this process. Okay, so you are back at the Verified Publisher with your (ahem, I mean their) new MPN ID. Again, you click on the link and add their MPN ID, and another error occurs: "The MPN ID you provided does not exist, or you do not have access to it. Please provide a valid MPN ID and try again." Okay, first, the MPN ID is valid; second, it exists; and third, what access do I need? This kitchen sink error message is not very helpful. But hey, there's a "learn more" link. Okay, so you go through hours of rummaging through the docs, and nothing is really apparent, but look at this—there's a Troubleshooting section. On the first bullet point, step four provides a link to verify the MPN (https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile), but this reveals a "Sorry, something went wrong. Please try again later" error page. With humility, you create one of your two allowed support tickets... and when going through the same steps, they mention something about access and start naming the people that could apply the Verified Publisher... so, we have to call our (non-technical) client again to come on the chat to be walked through how to add the MPN ID, and boom, it works. At this point, you're probably part happy, part embarrassed (for no reason), and part angry. Here's the problem—well, one of them. If you don't have access to do something, we are all trained to see disabled buttons/links; if the developers are really good, they change the CSS/cursor on hover, and if they're really, really good, they provide a tooltip explaining the access that is needed to click the button or link. BUT, for all that is good, don't provide a clickable link, a non-disabled textbox, and a non-disabled button to add something we can't add in the first place. Furthermore, do not provide an overly elaborate yet somehow vague validation message. I expect more from Microsoft. Secondly—and this is a self-preservation thing—requiring our clients also to become Microsoft Partners dilutes the value of being a Microsoft Partner. I see a cartoon of a word bubble above a technical person saying, "I'm a Microsoft Partner," and in the next frame, it shows a roofer, a janitor, a homemaker, and a plethora of a thousand people, all with the same word bubble saying, "Yeah, so are we!!!" Although this is a funny view of it, the reality is that it was hard enough to explain to clients why you want to add your MPN ID to their Azure subscription or what that means... but now, why would they, when they have that same feeling of ownership as with the App, and now armed with their own MPN ID? It truly is diluting the value of a Microsoft Partnership and, further, making it harder to justify adding our MPN ID to signal to MS who we are serving. This is directly tied to how we can obtain a Silver or Gold Partnership. This seems to have been built without consideration for agencies, small businesses, and clients outside the tech field.Repost: Make quick assist run as admin
Question: We need to be able to use Quick Assist in Windows 10 to do some administrative tasks, but if the end user initiates the Quick Assist session then the remote admin is limited to only what the end user has access to. Is there any way we can start Quick Assist as an administrator or elevate it to admin level during the Quick Assist session? Response: Quick Assistis my preferred application to resolve all technical issues remotely. It also allow me toRun as Administratorto install and configure hardware/software but there are few steps required as mentioned below: Run CMD at end-user's computer Type the below command: runas /user:domain\administrator cmd *domain will be any domain of your organization *administrator can be any administrator login. If domain is notavailabletype the below command in cmd. runas /user:local_user cmd Put the adminpassword. Now you have successfully launched cmd in administrator mode, you can run the below tasks. x:\MicrosoftEdgeSetup.exe(for software installation, where x is any drive letter from your computer). appwiz.cplforinstallingor uninstalling program. services.msc(Run or Stop a service) devmgmt.msc(Device Manager, to install/uninstall or upgrade the device driver) diskmgmt.msc(Disk Management) compmgmt.msc(ComputerManagement) regedit(Registry Editor) Above mentioned are just example, you can use the number of commands as per yourrequirement.
