In Federated Identity scenarios that require connecting to multiple Active Directory repositories using ADFS, there is no current way to use the User Profile service without connecting directly to the underlying LDAP/AD store. Instead, the User Profile service should support querying for user account information over Active Directory Web Services (ADWS) to better support Federated Identity in an organization using SharePoint and Claims-picking.

At the moment when you activate versioning within a Document Library you have limited Draft's control - essentially you can either see them or you can't. I would like to see this extended so you can, for example, specify whether Drafts are shown by default (as is the case now), or whether you see the Published version by default etc.

this is a big limitation with designer workflows as it is very common usecase to have while loop in most of the workflows (ex: do something while is not approved / till it is approved)

Provide an easy method for InfoPath 2010 Forms to pass Claims-based authentication credentials to WCF Data Services/WCF REST Services which utilize Windows Identity Foundation for Claims driven functionality.

I'd like to make a link between my Team Foundation Service project and a Sharepoint site for each project, which our customos can have access and know about the status project.

Provide native WCF SOAP Services for SharePoint rather than the current Classic .asmx services to reduce the amount of custom XAML that is required to communicate with SharePoint Web Services as well as to accommodate scenarios that the WCF SharePoint Data Services cannot currently handle.

When you change the default "Title" field using the SharePoint list wizard, have it also change the underlying "Title (Linked to item with edit menu) as well.

The Schema.Xml file is updated for the field with the ID of {fa564e0f-0c70-4ab9-b863-0177e6ddd247}. Just add the same entry for the field with the ID of {82642ec8-ef9b-478f-acf9-31f7d45fbc31}

When configuring External Content Types in SharePoint for BCS today via SharePoint Designer, one has to click on each and every table in the database to set up all necessary operations that can be used with External Lists.
Instead, there should be an easy way to perform this operation for all database tables in a database rather than having to go through this process one table at-a-time.

Currently, site columns, content types, and lists have XML schema based definitions, but Webs, User Groups, and probably other pieces of SharePoint have no corresponding XML definition. You should be able to define a Web (SharePoint Site) via XML.

The Content Type editor in VS has no way to change the Parent Content Type once the Content Type has been created. It should provide a dropdown that does all the necessary synchronization.

When an end-user opens an Excel workbook that is expected to be used with a particular Excel VSTO customization, Excel would check for the presence of the customization. If absent, it would offer to install it remoted. Presumably the workbook would contain the installation URL. Should also work with app-level add-ins.

When adding a SharePoint group to a resource calendar/group calendar that contains one or more Active Directory groups, one should be able to select an option to expand the individual users assigned to the AD group. This will allow all of the individual resources/users to be visible on the resource/group calendar. The current implementation only displays the name of the Active Directory group, thereby providing no insight into individual user/resource calendar details.

Currently, there is no out-of-the-box solution to sending meeting invitations (or any type of e-mail invite) from a SharePoint workflow. Instead, a custom solution has to be completely built to achieve this even though this is a common use case for SharePoint workflows esp. for users that are already using Outlook or even users that are using e-mail clients such as Lotus Notes.

Right now, once you've deployed a SharePoint object defined via XML into production, the XML becomes useless, as redeploying would cause any production data to get wiped out. The only options for further updates are SharePoint designer, the web UI, or a one-off script using the API.

VS should provide an option to synchronize already existing SharePoint objects with their XML definitions.

In Microsoft Dynamics CRM 2011, there is a concept of providing hierarchical security based on an organizational structure which allows security permissions to be controlled in a "roll up" fashion. However, the security permission model for SharePoint is largely flat with no innate support for an organizational/hierarchical security model. In order to make SharePoint more robust and further improve the integration points between Dynamics CRM 2011 and Microsoft SharePoint, SharePoint should provide hierarchical security similar to what is provided by Dynamics CRM 2011.

Currently, one is unable to configure SharePoint to natively connect to an external SMTP service such as GMail (or other Smtp e-mail providers) because GMail SMTP operates on different ports as well as requires SSL and authentication credentials. Instead, SharePoint 2010 requires IIS SMTP to be configured in order to use GMail as an external provider. However, since the .Net Framework provides the SmtpClient library to easily configure sending e-mails via GMail, SharePoint should also provide the same functionality and provide the corresponding user interface within Central Administration to support this capability.