Office installed on Azure VMs are losing their activation after a VM shutdown. This makes it impossible to create test VMs or use Office on a developer VM to develop/test/deploy(buildserver output) on Azure. Activation based on hardware assets such as harddrive and network MAC/IP combinations is outdated in 2014 and invalidates your VM images.

I sometimes use use SetDataAsync to write an email address into a cell. When this is done manually, Excel converts it into a clickable link. When it is done with SetDataAsync, this auto formatting doesn't happen. If would be great if it was just automatically triggered.

Currently it fires on scroll or changing formatting or cell width or a bunch of other random situations. Additionally, it should probably only fire when the user actually changes something, not when I write something with the API

At present, very few users give feedback and reviews on apps. As a result, other users are less likely to try them.

At every possible stage, there should be a mechanism for users to rate the app - provide a number of stars and comments. That could be an email reminder or a message that comes up next time they visit the store or something inside of Office 365. The more users that give feedback, the more that other people will feel encouraged to try.

Could you add a call to the Office API to collapse the selection? e.g. removeSelectionasync()

Our Eduction Task Pane apps work based on selections and we would like the ability to collapse the selection once the functionality we introduce has been completed.

At present our task pane apps target Word 2013 and Excel online, though we are coming from Word Object Model desktop type applications, so making the cross over.

i have requirement where i need to get exchange rooms (like we do through EWS by using getRooms)in my outlook mail app, right now there is no such functionality where through makeEwsRequest i can get the rooms.

The front page to the new store looks fantastic, it's nice, user-friendly and very intuitive. But that redesign doesn't extent to the page for each app.

When you click on an app, the page for each app is messy. It should be redesigned to encourage users to explore the screenshots, read the description and instructions, click relevant video, and ultimately add the app.

On the search result page for Office Apps, show the provider field of each App.

e.g. https://store.office.com/search.aspx?productgroup=SharePoint&catfltr=6&category=Editor%2527s%2BPicks

Can't tell which apps are made by Microsoft and which ones are made by which partner.

Is there a reason why you would not provide a common base for the two API's?
The Ewa namespace offers a lot of functionality requested in many ideas related to the Offie 2013 API - it seems you already have the code and the interface in the Ewa namespace ?

is there a "Contact apps for Outlook" for Office365?

Apps for Excel, Word, PowerPoint are available but for the moment there isn't the possibility to develop an app for Visio. Why ?

Extend the mailitem.to.addAsync() method to accept the custom email formats i.e 'Kiran123@/CO=OT' or.'RFAX:KIRAN@/FN=111/VN=1111' etc.
Currently "Office.cast.item.toMessageCompose(item).to.addAsyc()" method is not accepting any custom email address. It is throwing the following error message.

"No valid recipients were provided"

Apps for Office only run client side for Word, Excel and PowerPoint. OWA should support them as well.

Enhance the Office JS API to allow apps to send the selected user image as an object.

It's a pain to identify manually all Apps that are currently offering an update. Users should see a badge on the App Launcher as soon as an update is available.

Enhance the Office JS API to allow Excel to warn/prevent writing on cells with functions insde

Currently when you submit an app to office store, you have to enter app version, this has to match the version defined in manifest, this seems redundant to me, can we remove this field from the submission form. App manifest describes the version of the app and having to enter it again during submission seems redundant to me additionally the app validation fails when they don't match, don't believe this is called out anywhere in policy, I could be wrong.