Allow the generation of Vision Diagrams from ARM Templates. Ideally this would be via the command line so that this could be automated as part of the continuous delivery pipeline. Other tools like http://armviz.io allow the visualization of templates, but don't allow the saving or exporting of the diagram. The Developer Tools team is also looking at a similar solution. You guys/gals should talk. This would allow solution engineers and architects to generate diagrams from templates, reducing the burden to create Minimum Viable Documentation.

MS Excel Application have personal macro workbook (Personal.xlsb), MS Word Application have personal template with macros (Normal.dotm). Macros which contained in these storages can be called from any word's document or excel's workbook. But in Visio application there is no place where you can store macros available at the application level !

IMHO: If Visio Team add a similar feature it will be great !

Other than VBA, there is no easy way to create a Visio Solution in Visual Studio. One of the stumbling blocks is including Visio templates in the solution.

Add IsSelected and IsMouseOver cells to enable geometry and formatting changes to be applied while the shape is in a selected state (or mouseover).

Dynamically show and hide shape and sub-shapes elements based on the two states.

When using the Shape Replace feature, the User Defined Cells are not transferred to the new shape.

Give us a chance to follow up changes while merging two versions. 3rd party tools need to catch up. Currently the API does not even give a hint what has been changed.
We actually disable CoAuth in our solution since it makes our documents inconsistent.

I remember Microsoft Visio for Enterprise Architect, and how i can modelate a sql database using Visio.

I don't understand why you remove this feature, today it's only able to reverse engineer a database using Visio Pro for Office 265, but it's not possible forward to database.

I know a lot of people with the same problem, i'm still using Visio 2003 for Enterprise Architects today (now in 2017), and i will be happy if you give us this feature back!

Give us programmatic control which quick shapes are being displayed. We need to manipulate which shapes may be connected to other shapes in a specific context. E.g. in EPC you may never connect an Event with another Event. This functionality is provided by many process modelling tools.

Quick Shape information is currently stored in an encoded string in the registry

It would be helpful to provide a function via the shapesheet for connections to be able to determine if they have a connection or not.

MS stated future for extending Office applications in via a Rest Api and support for MS Graph.
Imagine asking a Skype Bot to draw a diagram of network devices that can be discovered, or create an orghart of someone's team, or create a flowchart of steps required to achieve a goal...

I want to create custom Org chart wizard.
Because Standard function cannot suport Japanese rule.

I produce diagrams never intended to be printed out - network diagrams, database schema, et al. It is extremely constraining to have to be juggling shapes around to fit in some arbitrary A4 / A3 / whatever sized paper background and always see those edges locking in my work. Let me just have an infinite blank canvas. Or if that exists in Visio, I cannot find it.

To allow tool makers to access things like scroll position (scroll a given cell to view), cell background color, cell tooltips, context menus etc.

Currently, the Data Graphics window closes and becomes disabled as soon as you start recording a macro..so you cannot create VBA code to automate standard DG configurations that may be needed. This is very annoying when you have tens of drawings to produce with identical configurations and you are trying to make it easy for Visio beginners to perform on a regular basis.

The purpose I'm thinking for this, is to make possible to get strings of Name or NameU properties automatically with a dynamic connector, making possible to get and send data between shapes by connecting them with a dynamic connector, using only shapesheet functions.

The idea of hiding connection points and only showing them when the end of a connector is dragged near to a shape works fine. However, this does not work for control points that can be glued, seems to be an oversight. The connection points should be shown when the control point is moved near to the shaoe.