Doing JAC cleanup - This was fixed with release of the SharePoint Connector.

Closing this with the release of the Generally Available Release of the Confluence SharePoint Connector in Aug-08.

The initial sharepoint integration is available for download:

http://www.atlassian.com/sharepoint

As noted in CONF-5932 (Sharepoint-like functionality) back in July, we do NOT believe this issue on Sharepoing Integration should be considered as "incorporates" the other one.

We are not currently using Sharepoint, and would not have to consider it if the reserved check-out/check-in functionality for Windows files requested by CONF-5932 and CONF-6012 were availability within Confluence itself. In every other aspect, Confluence is far better, so we would much prefer to not have to go through the additional expense and complexity of adding Sharepoint to our environment.

However, our need for reserved check-out/in funcitonality is urgent, so if Confluence doesn't implement it soon I guess we be forced to implement that Sharepoint - at which time we will vote for this "integration" issue.

We are going to use Sharepoint2007 in march. And the production date for confluence is february.

Sharepoint is going to be used as a intranet and CMS.
Confluence is going to be our knowledge tool.

What we need desperatly is that the search engine is also searching the Sharepoint data (SQL Server) and handles authorization in SP2007.

I hope Atlassian wil come with a solution for this problem.

I have tried SharePoint's "Wiki Page Library" and found myself terribly missing Confluence's interface, mark-up language and all the other neat features. If we could use SharePoint as a back-end to our Confluence instance, I would be eternally grateful and call you guys my new best friends.

Well, the first integration point should be between search engines.
My company is currently building a global knowledge base and Sharepoint will be part of that. Now, I think Confluence could meet some requirements that SharePoint won't (f.i. easily capture ad-hoc, unstructured information, the knowledge usually kept in the head of developpers).
However, the Knowledge Management team would like to keep one single entry point in the Knowledge Base, implying to get one search engine able to find all relevant documents both in Confluence and Sharepoint.

What does "Sharepoint integration" mean? 
What exactly does this customer what to accomplish?
How do they envision using Confluence and Sharepoint together? What tasks would they be performing in each environment?