Share your ideas and vote for future features

It would be nice to add/update user-defined fields to the contact object. ... View more

Flow may be used to sync a sharepoint contact list to users mailbox contact folder. I think it would be a good idea to provide a template that does just that. Sync a user selected contact list in exchange online with a user selected contact list in sharepoint online. Either one-way or two-way. A preconfigured template should be shared between users in a company so that activating the sync is very simple for new users.   Most users needing shared contact lists on the phone - in their mailbox for ActiveSync to sync it - would profit from such a solution. So the number of potential users is huge! ... View more

When a contact is created or updated, the action requires to add a “Home phones Item”. I think this is a bug as there is no obvious reason to require this property. Furthermore the documentation also states that this property is optional for both actions. ... View more

Street, City, State, CountryOrRegion, PostalCode appear three times: For both create and update contact, these properties appear three times without apparent difference! The documentation states that these are the same key. In reality, the first group is for the home address, the second group is for the business address and the last group is for the other address. So this is a display bug and also a bug in the documentation.   ... View more

On the create contact action it is currently possible to provide an ID which is clearly not honored in the contact creation process (at least for the ids I provided). Either this property should be removed from the action, or the documentation needs to specify a working format for this field.   On the update contact action the Id property occurs twice. Once as mandatory (for identifing to contact to update), once as optional. I recon the optional Id is for cases when the Id should be updated. But as with create contact, this doesn’t seem to work. Thus this property should be removed from the action, or the documentation needs to specify a working format for this field. ... View more

Would like to be able to extract all attachments from an email and build one single archive that i can use further in the flow chain (within SharePoint, Exchange, Dropbox etc).      Note: this idea started from this "Building flows" topic: https://powerusers.microsoft.com/t5/Building-Flows/Create-an-archive-file-from-email-attachments/m-p/33558#M3113. ... View more