officedev / office-store-docs Goto Github PK

Microsoft AppSource and Office Store Documentation

License: Creative Commons Attribution 4.0 International

PowerShell 100.00%

office-store-docs's Introduction

Microsoft 365 App Stores documentation

Welcome to the Microsoft 365 App Stores documentation. Here you can find content related to publishing apps and add-ins to AppSource. When you add your solution to AppSource, you also make it available in the Microsoft 365 app store within products like Teams, SharePoint, Word, Excel, PowerPoint, and Outlook. For the best experience, we recommend that you view this content on Microsoft Learn.

Publish. Certify. Monetize.

Additional resources

Give us your feedback

Your feedback is important to us.

To let us know about any questions you have or issues you find in the documentation, submit an issue in this repository.
We also encourage you to fork, make the fix, and do a pull request of your proposed changes. For details, see Contribute to this documentation.

Copyright

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

office-store-docs's People

Contributors

Stargazers

Watchers

Forkers

davidchesnut lauragra maireadb richmoemsft silecard jmumenthaler majordamage alburm cwlock reezaali lindalu-msft hodlhodl esthergaddindla carlrabeler reneesundaram jasjitchopra wamaina linda-editor alexjerabek alan1mulhall elizabethsamuel-msft thpubs the-mojoo prkosh michaelriceio rokeates parthpandyamsft timosalomaki laujan qianw211 anbene jasonwhowell dsindona lgerrard isabella232 emuench dcthegeek v-jrushing peteantoniou atikmapari tryweirder surbhigupta12 heath-hamilton arkaroyspektra v-rodriguezd v-abirade julcsc dannyevers ghostface781 v-sumukh tryweirdier alexbuckgit douglasanunciacao superyyrrzz meganbradley

office-store-docs's Issues

Will requirements to test Office Addins on Windows 7 be dropped?

With Windows 7 leaving extended support on January 14th, 2020 (basically in a month), will the requirements for testing Office Online add-ins in Windows 7 be dropped as well?

Not clear on when/where add-ins can be activated.

It appears that addons cannot be activated when you open either a msg or eml attachment. It looks like this is not documented anywhere.

Send customer to the rating page from the add-in

The documentation suggests to send the customer directly to the rating page, after a while the user using the add-in.

How can I determine the link for my add-in's feedback/rating page?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc80e015-a389-193a-5e65-93b16e6eff59
Version Independent ID: 188d2a91-ad03-750f-8d78-d3d5f134624b
Content: Create effective listings in AppSource and within Office
Content Source: docs/create-effective-office-store-listings.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

Email verification for becoming MPN developer does not work. I get an error when i click the verification button. Also, when I try to 'resend verification email' that does not work either. Anybody have experience with this?

[Enter feedback here]

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 23aff8f8-a2cc-2722-d806-08d4a8e519ad
Version Independent ID: 913f49b5-797d-351f-d8f0-59e68f7153f0
Content: Make your solutions available in Microsoft AppSource and within Office - Microsoft AppSource
Content Source: docs/submit-to-appsource-via-partner-center.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Monetising Office addin using own payment model

I would like to monetise Excel add-in, by creating my own payment and licensing model. I would like allow users to download add-in for free from office store, use it for some time free of charge and later when the initial free offer is expired I will give user and option to buy a licence from my own portal. The payment collection system will be implemented using trusted payment collection provider system like Strip or other. Can I implement my own licensing / payment system? My adding will contact my licensing API check that the user is fully licensed before allowing user to user the services. Is this model comply with MS monetising guidance?

No Azure Blob Setting in Partner Settings

When I load up the Partner Center after creating an Azure Blob in the Azure Portal, I only have five options, with the missing option being 'Azure Blob'.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a6b53e9c-2999-4659-f3b2-ad8b781539b9
Version Independent ID: 271e7a8d-d27e-d00b-8680-f92f6f3b00a6
Content: Add setup details for your Office solution - Microsoft AppSource
Content Source: docs/add-setup-details.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Validation Policies Should Reference iOS Guidelines

validation-policies.md needs to incorporate the additional iOS guidelines given in https://github.com/OfficeDev/office-js-docs/blob/master/docs/develop/develop-office-add-ins-for-the-ipad.md

Unhappy: Cannot publish Add-In to Office Store :-(

[Dear MS,
I am a private individual and do not have a company email.
This means I cannot register in https://partner.microsoft.com/en-us/dashboard/directory for Office Store. This in turn means I cannot publish my Add-Ins.

I find this wholly unfair.

Can you help me publish my add-on please?

Yours Sincerely
Stewart Muscutt
]

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e562d696-605e-c4ab-226d-241e633e2b0d
Version Independent ID: 0d9b1c63-d87c-e705-cac6-8b940449a115
Content: Store step-by-step submission guide - Microsoft AppSource
Content Source: docs/add-in-submission-guide.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Respond to customer reviews in AppSource - needs to be updated perhaps

When we visit the app page and go over comments, logged in as the same user used to submit the app to the store, we only have a "report abuse" link near reviews. the "comment" link is not available.
Please clarify where this link is or why this option is not available.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc80e015-a389-193a-5e65-93b16e6eff59
Version Independent ID: 188d2a91-ad03-750f-8d78-d3d5f134624b
Content: Create effective listings in AppSource and within Office
Content Source: docs/create-effective-office-store-listings.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

Partner Center role required to add new solution should be documented

The article mentions that one should create a new solution in Partner center. I think the documentation should state what role the user needs to have in Partner Center in order to have the appropriate permission to perform this operation.

I also tried to find documentation on this by looking here:

https://docs.microsoft.com/en-us/partner-center/permissions-overview

But, it's very hard to see what role is required to add a new solution.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 212133ca-1a51-d0fd-4108-32508cbc20a7
Version Independent ID: 45ee8995-57c3-2f16-779d-060cf7be1721
Content: Submit your Office solution to Microsoft AppSource via Partner Center - Microsoft AppSource
Content Source: docs/use-partner-center-to-submit-to-appsource.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

[LOC] Broken link

There is a broken link in an article

repro steps:

go to https://docs.microsoft.com/en-us/office/dev/store/add-license-checks-to-office-and-sharepoint-add-ins
Search for "getUserIdentityTokenAsync" link
Click on the link

Actual results:
Link redirects to a non existing page
Expected results:
Link should redirect correctly

GH article:
https://github.com/OfficeDev/office-store-docs/blob/live/docs/add-license-checks-to-office-and-sharepoint-add-ins.md

manifest file shows in uploading status from more than 24 hours

Hi Team,
we are currently working on deploying our sample add-in to office store. we have added our package manifest file in packages tab. Although it shows in uploading status from last 24 hours and we didn't received any error while uploading.

Please suggest. we have also tried removing the package and adding again.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1c8e5a54-3d66-8917-7ecc-1b8d01420338
Version Independent ID: 4a71b13e-522f-042f-0971-81061466a902
Content: Upload your package to Microsoft AppSource - Microsoft AppSource
Content Source: docs/upload-package.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Indivudal account for developers

Individual account for developers in Partner Centre does not allow to submit add-ins for Word - there is no interface for that (more precisely, it always redirects to creating company account) unlike in company account. I've created an add-in for Word but cannot submit to Office Store as an individual. It's not clear from this documentation.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd82b4bc-7340-4aff-bc43-5cfea08c24bf
Version Independent ID: cf756c44-bdef-dd4e-875b-3a792be27bca
Content: Open a developer account in Partner Center - Microsoft AppSource
Content Source: docs/open-a-developer-account.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Contradictory recommendation of long description

Under "Effective Long Descriptions" you say "Most users read between 300 and 500 words.". In the table under "Apply guidelines for title and description length", for Long description the recommended length is "300-500 characters". These recommendations are contradictory. I presume the table should say "300-500 words" rather than "300-500 characters"

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc80e015-a389-193a-5e65-93b16e6eff59
Version Independent ID: 188d2a91-ad03-750f-8d78-d3d5f134624b
Content: Create effective listings in AppSource and within Office - AppSource
Content Source: docs/create-effective-office-store-listings.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

[LOC] Link redirects to a non existing page

There is a link redirecting to non existing article

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/upload-package
Search for "Create the package for your Microsoft Teams app"
Click on the link

Actual results:
Link redirects to a non existing article
Expected results:
Link redirects to a valid article

GH Article
https://github.com/OfficeDev/office-store-docs/blob/live/docs/upload-package.md

Who to turn to for support?

In the seller dashboard, it says "Account pending approval", but on my developer account (https://partner.microsoft.com/en-US/dashboard/account/management) the account status is "Authorized". It has been this way for days now, and I'm at a loss to figure out what I should do. Who can I turn to for support on this matter?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 46ba792e-3604-2387-df01-658d8a58d413
Version Independent ID: a4bd95e7-bc69-9aaf-3747-f9eab9f67556
Content: AppSource submission FAQ - AppSource
Content Source: docs/office-store-submission-faq.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

encodeURIComponent not working as expected for verification service on node server

Hello,

I am currently running a node/express server to do license verification for my application. I am having issues I was able to work around but it does not follow the guidelines provided so I wanted to check if I am missing something.

Currently I am getting the et parameter and base64 decoding it

var token = new Buffer(req.query.et, 'base64').toString('ascii');

Then according to the guidelines I need to url encode this to send it to the verification service. If I use encodeURIComponent as suggested, I get the following url (this is based off of the sample token provided in the docs).

token = encodeURIComponent(token);

This does not work (IsTest is false). However if I use some regex magic I do get a working response.

token = encodeURIComponent(token).replace(/%00|%0D/g, '').replace(/%20/g,'+');

https://verificationservice.officeapps.live.com/ova/verificationagent.svc/rest/verify?token=%3Cr%3E%0A++%3Ct+%0A++++aid%3D%22WA900006056%22%0A++++pid%3D%22%7B4FB601F2-5469-4542-B9FC-B96345DC8B39%7D%22%0A++++cid%3D%2232F3E7FC559F4F49%22%0A++++et%3D%22Trial%22%0A++++ad%3D%222012-01-12T21%3A58%3A13Z%22%0A++++ed%3D%222012-06-30T21%3A58%3A13Z%22%0A++++sd%3D%222012-01-12T00%3A00%3A00Z%22%0A++++te%3D%222012-06-30T02%3A49%3A34Z%22%0A++++ts%3D%220%22%0A++++test%3D%22true%22%2F%3E%0A++%3Cd%3EVNNAnf36IrkyUVZlihQJNdUUZl%2FYFEfJOeldWBtd3IM%3D%3C%2Fd%3E%0A%3C%2Fr%3E

Just wanted to clarify if I am doing something wrong or the documentation is out of date.

[LOC] Invalid link in an article

There is a broken link within an article.

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/validation-policies?context=outlook/context
Search for the "Guidelines for Power BI visuals with additional purchases"
Click on the link

Actual results:
Link redirects to a non existing page
Expected results:
Link redirects correctly

GH article:
https://github.com/OfficeDev/office-store-docs/blob/master/docs/validation-policies.md

Outlook-email-paid-add-ins

As I understand from the documentation if I want to sell through Microsoft and not to implement my own payment model the add-in will be accessible only to users with work/school emails and people with outlook emails won't be able to use it, is this correct?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6e475466-5221-4374-a8e2-fbc5a5645683
Version Independent ID: 26a61b4c-d607-b2c4-4432-542cd1072726
Content: Monetize your Office 365 add-in through Microsoft Commercial Marketplace - Microsoft AppSource
Content Source: docs/monetize-addins-through-microsoft-commercial-marketplace.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Publishing JS Add-In on Microsoft Partner Center

Situation:
Microsoft Excel JS Add-in - Trying to publishing on App Source - Fonctionning add-in (local/ azure)

Issue:
The following error is raised when trying to publish the app on Microsoft Partner Center and trying to upload the package (e.g. in my case manifest.xml): "Package acceptance validation error: manifest.xml is an unknown package type. Please name your file with the appropriate file extension."

Question:
What is the correct way to publish on App source for Excel JS Add-in? Is it documented somewhere?

Thank you

Office 365 validation test results "Contact us"

I received feedback for an AppSource submission, and there are a couple of ambiguous comments in the document that I need more information about. Inside the PDF, it says:

Please address the validation errors before we publish your solution to the storefronts on AppSource and within Office products.

Next steps:

Contact us. We can help you resolve your validation issues more quickly.

Address the issues listed and resubmit your solution.

Confirm you’re following best practices. Apply our best practice guidelines to your UX design.

The problem is, there is no contact information or link for WHO to contact. It just says "Contact us".

Who should I be contacting regarding in-progress submissions, and where do I find this contact information?

Broken link

Link redirects to a non existing page.

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/validation-policies
Search for "SharePoint Add-in design guidelines"
Click on the link

Actual results:
Link redirects to a non existing page
Expected results:
Link should redirect to a existing page

GH article:
https://github.com/OfficeDev/office-store-docs/blob/live/docs/validation-policies.md

Mobile add-in dialog box for authentication

I am developing calendar add-in for outlook mobile version.

And I found that When I turn on this toggle and using Office.context.ui.displayDialogAsync to open dialog box for login in authentication, it will always jump up to other browser to open login in page instead of display inside outlook app, and outlook add-in toggle will turn off just like connection lose.
This issue was just happened and only on Andriod machine, it used to dispaly in outlook but recently its bahavior was changed. And some add-ins like Zoom will still display inside outlook.

By the way, if I repeat to turn on toggle for 2-3 times, it will open dialog inside outlook app again, just as the screenshot, it's so wired...

I wondering if this is due to my add-in is just for development and not submit to MS store yet, is there any scecurity update on MSFT?

Monetizing VSTO Add-Ins

It is really unclear in this page that VSTO add-ins are not supported (unless they are) but I can't figure out how to publish one for monetization. Is there a way to monetize VSTO Add-Ins ? If so do you have a sample walk-through ?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fd6cdb21-e624-a60d-9dff-e880b28643be
Version Independent ID: 56b84478-0f73-93e1-6393-0a4e50fe4426
Content: Make your solutions available in AppSource and within Office - AppSource
Content Source: docs/submit-to-the-office-store.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

What is the estimated timeline on this working for Appsource and in-client?

I chose to setup the Azure Table option for our Excel add-in, but at the moment it looks like it only stores placeholder information. Is there are timeline for when this will be implemented? Also, how will the in-client piece work? My guess is that it will still use the "src" and "mrktid" parameters in the url?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a79d9f7f-704a-9e9e-3f8a-49969540cbc7
Version Independent ID: 6ce4198c-665e-097c-1db1-d47c5c8d043c
Content: Add lead management details for your Office Add-ins in the Seller Dashboard
Content Source: docs/add-lead-management-details.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

"Why publish" docs about stores are super confusing

I am trying to understand the different options for publishing an Excel add-in, and these docs left me more confused than when I started. I'll try to explain why.

Your app can be distributed directly through the Microsoft 365 app stores inside of Outlook, Excel...

I have never seen those and I had no idea where to find them in Excel. I eventually found "Get Add-ins" under the Insert ribbon (very unexpected location); I think that's the Microsoft 365 app store but nowhere in the UI does it say "Microsoft 365 app store".

In addition to the Microsoft 365 app store, Microsoft AppSource is another distribution point for your app. It is the official app store for Microsoft 365 apps and solutions.

So the "Microsoft 365 app store" is not the official app store for Microsoft 365 apps, AppSource is? That's super confusing. This document could really also use a link to AppSource.

When you submit your app for validation and it is approved, your app is automatically added to both the Office and Microsoft AppSource stores.

This seems like the terminology changed partway through the document. What was previously described as the "Microsoft 365 app stores" is now the "Office stores"?

Finally, if I read the "Deploy and publish Office Add-ins" page it doesn't mention the "Microsoft 365 app stores". So I am left with the suspicion that the "Microsoft 365 app stores" are somewhat deprecated.

I think any developer who reads this doc is going to be left with multiple unanswered questions:

Why are there multiple stores?
Do I need to worry about any differences between the stores? It really sounds like the "Microsoft 365 app stores" are different from AppSource in some meaningful way (beyond installation UI) but the docs don't offer any clarity there.
Do these stores have any relation to the Microsoft Store included with Windows?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b4424fa-be94-e829-52a1-5eb948301750
Version Independent ID: 236f068c-fcf2-7155-d767-f53616b65696
Content: Publish your app to the Microsoft app stores - Microsoft AppSource
Content Source: docs/why-publish.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: mingshen

How can one delete published solutions

Hey everyone,

It is mentioned in the doc that if you've already published your solution to Microsoft AppSource, you can't remove it from Partner Center but there's no guidance on where and how to remove it, unfortunately.
Is a Support Request required in order to get a solution deleted?

Many thanks!

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 52857d74-7e76-cbe7-5f3d-bce27e369a46
Version Independent ID: 174b8aa7-d22c-7a0d-fdb9-66c3e0cbfd99
Content: Manage names in Partner Center - Microsoft AppSource
Content Source: docs/manage-solution-names.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Question for mobile calendar add-in deployment

Our add-in has been published to MS add-in store. And we plan to release a mobile version.
We deploy our add-in via MSFT partner center.
From these screenshots, it seems we need to provide a apple developer id because our manifest has mobileFormFactor element. And I wondering if our add-in does not need to be in the Apple Store, do I need to select this checkbox for Apple Store Availability?
And all I need to do is just provide apple dev id on account settings? Is there any limitation of this apple dev id or other requirements for publish mobile version?
Thanks in advance!

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a6b53e9c-2999-4659-f3b2-ad8b781539b9
Version Independent ID: 271e7a8d-d27e-d00b-8680-f92f6f3b00a6
Content: Add setup details for your Microsoft 365 solution - Microsoft AppSource
Content Source: docs/add-setup-details.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: mingshen

Feedback on documentation - "Authorize to Microsoft Graph" is confusing and seems out of place

Just trying to help with the docs...

The section title is "Build an Azure AD connected add-in" and goes on to describe the 3-states of your add-in. Got that. Then the section ends with "to authenticate with Azure AD, see "Authorize to Microsoft Graph" which goes to a page titled "Authorize to Microsoft Graph without SSO"??? Not clear why the add-in cares about Microsoft Graph. I believe it's to allow the user to login to AAD to get user information from a tenant but that's not really clear.

Maybe a sentence or two as to why you're doing this and why the link to "Authorize to Microsoft Graph".

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6e475466-5221-4374-a8e2-fbc5a5645683
Version Independent ID: 26a61b4c-d607-b2c4-4432-542cd1072726
Content: Monetize your Office 365 add-in through Microsoft Commercial Marketplace - Microsoft AppSource
Content Source: docs/monetize-addins-through-microsoft-commercial-marketplace.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Can I edit release date after an app is approved?

If I want to start the approval process before knowing an exact release date, I might want to:

Submit my app for approval with a distant release date
Complete the full approval process
Later, edit the release date to move it forward

Is it possible to edit the release date after an app is approved? If possible, does that require going through the approval process again?

(P.S. Thanks for the great docs!)

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2c1670eb-6ba2-88aa-6162-46bd4e2395dc
Version Independent ID: 5aaa87d0-35d8-32bf-9fa0-56a1473a984e
Content: Use the Seller Dashboard to submit your solution to AppSource
Content Source: docs/use-the-seller-dashboard-to-submit-to-the-office-store.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

Inaccurate reference to Stack Overflow

At the bottom of this page, guidance is given, pointing people to Stack Overflow for non-programming purposes:

If you have general questions about policies, processes, or validation requirements, you can engage with the Microsoft AppSource validation team via Stack Overflow. Tag your question with "Office-Store".

Unfortunately, policy/procedure types of questions will likely be downvoted and/or closed by the community, as they would be considered off-topic. Perhaps these questions could be directed to a more appropriate forum...

I've now seen several questions posted, expecting someone from Microsoft to address specific validation failures. These are all off-topic for Stack Overflow.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 23aff8f8-a2cc-2722-d806-08d4a8e519ad
Version Independent ID: 913f49b5-797d-351f-d8f0-59e68f7153f0
Content: Make your solutions available in Microsoft AppSource and within Office - Microsoft AppSource
Content Source: docs/submit-to-appsource-via-partner-center.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Broken Link

Link redirects to 404 error message.

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/validation-policies
Search for "Craft effective AppSource images"
Click the link

Actual results:
Link redirects to 404
Expected results:
Link should redirect to a valid page

GH article:
https://github.com/OfficeDev/office-store-docs/blob/live/docs/validation-policies.md

[LOC] Invalid link in an article

There is a broken link within an article.

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/add-license-checks-to-office-and-sharepoint-add-ins
Search for the "getUserIdentityTokenAsync"
Click on the link

Actual results:
Link redirects to a non existing page
Expected results:
Link redirects correctly

GH article:
https://github.com/OfficeDev/office-store-docs/blob/master/docs/add-license-checks-to-office-and-sharepoint-add-ins.md

Lead Management information doesn't save despite the positive communicate.

When You choose "Edit Lead Management information" in app details, after information and credential input there is a "Your data has been saved successfully" communicate and after returning to the edit page there is no information at all only unchecked "Leave management" I was using a Chrome browser 59.0.3071.115

The Dynamics PDF has a broken link

I can't download (or find independently) the MicrosoftMarketplacesLeadIntegrationSolution_1_0_0_0_target_CRM_6 file required to setup Dynamics for capturing new leads. Is there an updated version of this document?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a79d9f7f-704a-9e9e-3f8a-49969540cbc7
Version Independent ID: 6ce4198c-665e-097c-1db1-d47c5c8d043c
Content: Add lead management details for your Office Add-ins in the Seller Dashboard
Content Source: docs/add-lead-management-details.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

[LOC] Link redirects to 404 page

There is a link which redirects to a non existing page

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/upload-package
GH https://github.com/OfficeDev/office-store-docs/blob/live/docs/upload-package.md
See the "Create the package for your Microsoft Teams app" link

Actual results:
Link redirects to a non existing page
Expected results:
Link redirects a existing page

Image:

How can I host app on appsource store as independent contribute

[Enter feedback here]

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: da4b471b-b69a-2843-e9dc-dd5816a3ba53
Version Independent ID: 5d9bf895-6877-8920-1ab5-b238a3d6960d
Content: Create your AppSource listing - AppSource
Content Source: docs/office-store-listing.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Recommendation on updating the add-in

Hi. T

his page describes how to update my submission to the AppSource.
It would be nice if there were some words, how should I handle the submission if I want to update my add-in.

Here is an example scenario:
We submitted an add-in successfully. Then we implement something cool, but it needs to change something in the manifest. When we submit the new manifest it contains the url to the add-in code. So it is necessary to update the addin code before the submission, which means the live audience got the new add-in before the approval.
What is the good/recommended way to upgrade the add-in?

Another thing not clean for me:
The submission form has a version field, which gets the value from the manifest. If we updating the add-in we may change the version which may be shown in the add-in UI. We may update something small, maybe something big.
What is the recommended process to update the version in the manifest?

Thanks.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 62273393-b7a5-bd0a-84d7-42055370c860
Version Independent ID: 27aa3fc1-e883-5076-234f-e158eff79c0f
Content: Update or unpublish your add-in in Seller Dashboard
Content Source: docs/update-unpublish-and-view-metrics.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

What is lead management and does it actually work?

I am the developer of a Microsoft Teams app and I have configured Azure table details for lead management.

I know customers have installed the app since I setup lead management but there is no data in the azure table or in the analytics section of the app.

No guidelines about manifest version # changing

I just had an application rejected because I changed my manifest but did not increment my manifest version. While it may be obvious to some that you should increment your version, while there may be technical reasons this should be done, nothing in the guidelines even suggests this.

Recommendation: If this is an actual requirement, add it to the guidelines.

Specifically referencing this page: https://dev.office.com/officestore/docs/validation-policies

Where can I find who paid for my add-in?

Hello,

I have a paid add-in Funfun with a free trial period. It allowed me to gain some money each month (I got payment notification from Microsoft Partner Center).

However, I don't know where to see who have past the trial period and paid this money. This information is obviously essential for my business.

I do have lead information sent to an Azure table. It shows who added my add-in, whereas it does not show who have past the trial period and paid:

Do you know where I can find this important information?

Cheers

Tie

Question on updating add-in doesn’t clarify case of unpublished previous version and user not updating

The AppSource submission FAQ question on what happens when updating an add-in doesn’t entirely clarify what happens when the previous version is unpublished, and the user does not choose to update. Will the user continue using the previous version, or is the user blocked from using the add-in until they choose to update?

I’m referring to the following question (source version, online):

What happens when I update my app to a new version in Microsoft AppSource?

The following is the update process for Office Add-ins:

You submit your revised add-in and add-in manifest to Microsoft AppSource via Partner Center. The revised […]

You can choose to continue to offer the previous version of your app in Microsoft AppSource, or you can unpublish the previous version.

When an existing customer launches the updated app for the first time, a notification appears either in the task pane or the body of the document that prompts the user to update their app. When the user chooses Update, the latest version of the app launches.

Could you, for the third point, clarify what happens when the user does not choose to update? In particular if, for the second point, the previous version was unpublished? Will the user continue using the previous version, or must they accept the update to continue using the add-in?

Also: what happens if the updated add-in is no longer supported by the Office application version the user is using (due to an updated Requirements element in the manifest)?

On-send restrictions

Shouldn't this page also reference this warning "Add-ins that use the on send feature aren't allowed in AppSource"? (from https://docs.microsoft.com/en-ca/outlook/add-ins/outlook-on-send-addins?tabs=windows)

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f4c63f26-72a6-8963-e4f0-88d4aa4c6a38
Version Independent ID: 9bbc7ac3-9f91-bcde-44d3-3952c9133257
Content: Validation policies for apps and add-ins submitted to AppSource (version 2.2) - AppSource
Content Source: docs/validation-policies.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Menu Typo

There is a typo on the LH menu for this page - it reads "Mange" instead of "Manage"

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 52857d74-7e76-cbe7-5f3d-bce27e369a46
Version Independent ID: 174b8aa7-d22c-7a0d-fdb9-66c3e0cbfd99
Content: Manage names in Partner Center - Microsoft AppSource
Content Source: docs/manage-solution-names.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Documentation states that ts is not relevant for office addins

Here are more details regarding this issue: https://stackoverflow.com/questions/49369921/test-token-for-outlook-add-in-always-returns-null-tags

Test token validation returns nothing via the license validation service for outlook add-in

I am trying to get test token validation working for an Outlook office add-in.

Decoded String:
VNNAnf36IrkyUVZlihQJNdUUZlYFEfJOeldWBtd3IM=

Encoded String:
%3Cr%3E%3Ct%20aid%3D%22WA900006056%22%20pid%3D%22bd1fedd2-ff5f-4b8e-ac48-c2b47ee0ce91%22%20oid%3D%223DBFC30C-DBE9-419E-A5FB-1DB48BEDEC1B%22%20did%3D%22xxxxxxx.onmicrosoft.com%22%20et%3D%22Trial%22%20ad%3D%222018-01-12T21%3A58%3A13Z%22%20sd%3D%222018-01-12T00%3A00%3A00Z%22%20te%3D%222018-06-30T02%3A49%3A34Z%22%20test%3D%221%22%20%2F%3E%3Cd%3EVNNAnf36IrkyUVZlihQJNdUUZlYFEfJOeldWBtd3IM%3D%3C%2Fd%3E%3C%2Fr%3E

No matter what and how I pass this to https://verificationservice.officeapps.live.com/ova/verificationagent.svc/rest/verify?token={token} it just does not return anything with any value populated.

Is the documentation stale on the string format or am I missing anything? The documentation says 64 bit encoding is not required for Office Add-ins.

[LOC] Link redirects a non existing page

There is a link which redirects to a non existing page.

Repro steps:

Go to https://docs.microsoft.com/en-us/office/dev/store/submit-sharepoint-add-ins-for-office-365-operated-by-21vianet-in-china
See the "21Vianet" link

Actual results:
Link redirects to a non existing page
Expected results:
Link redirects a existing page

Seller Dashboard for U.S. Government Environment

We are using the Seller Dashboard to manage the client id and client secret, and recent we found the SharePoint Online App is not working in U.S. Government environment like GCC High Office 365 tenant. Is there any separated Seller Dashboard for U.S. Government? Thank you!

The other user is facing the same issue here https://sharepoint.stackexchange.com/questions/283831/sharepoint-add-in-client-id-and-secret-for-us-gov-tenancy

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bf555ecc-94e0-0f23-ab27-b1d2e483fbc5
Version Independent ID: e0cb668e-05e3-8412-04de-6e24aea97ea5
Content: Create or update client IDs and secrets in Partner Center - Microsoft AppSource
Content Source: docs/create-or-update-client-ids-and-secrets.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

Bookmark

Hyw guys can I offer a suggestion. can we bookmark theses pages

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: da4b471b-b69a-2843-e9dc-dd5816a3ba53
Version Independent ID: 5d9bf895-6877-8920-1ab5-b238a3d6960d
Content: Create your AppSource listing
Content Source: docs/office-store-listing.md
Service: unspecified
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

'Overview' link does not link to a page with the 'Create New' option

could be to do with some behind-the-scenes updates happening to that page but this is the link location:
https://partner.microsoft.com/dashboard/office/overview

and this is the link it sends you to:
https://partner.microsoft.com/en-us/dashboard/directory

What's more, i seem to be unable to 'get started' with the 'Office Store' developer program because it asks me for company details when my company has already signed up and is affiliated with Partner Center... PLEASE HELP

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 212133ca-1a51-d0fd-4108-32508cbc20a7
Version Independent ID: 45ee8995-57c3-2f16-779d-060cf7be1721
Content: Submit your Office solution to Microsoft AppSource via Partner Center - Microsoft AppSource
Content Source: docs/use-partner-center-to-submit-to-appsource.md
Product: office
Technology: ****
GitHub Login: @o365devx
Microsoft Alias: o365devx

officedev / office-store-docs Goto Github PK

office-store-docs's Introduction

Microsoft 365 App Stores documentation

Publish. Certify. Monetize.

Additional resources

Give us your feedback

Copyright

office-store-docs's People

Contributors

Stargazers

Watchers

Forkers

office-store-docs's Issues

Document Details

Document details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Document Details

Recommend Projects

Recommend Topics

Recommend Org