Monday, March 28, 2011

Microsoft Offered Updated Office 365 Beta Service Descriptions on 3/21/2011

The Microsoft Download Service offered the following *.docx files for download on 3/21/2011 with no fanfare:

These documents provide a detailed description of the features and functionality of Office 365 services currently in beta.

File Name: Size: Download
Microsoft_Exchange_Online_Beta_Service_Description.docx 2.1MB Download
Microsoft_Lync_Online__Beta_Service_Description_Final.docx 137KB Download
Microsoft_Office_Professional_Plus_Beta_Service_Description_Final.docx 924KB Download
Microsoft_Office_Web_Apps_Beta_Service_Description_Final.docx 185KB Download
Microsoft_SharePoint_Online_Standard_Beta_Service_Description_Final_ Mar2011-update.docx 2.5MB Download
Office 365 Beta Enterprise Support Service Description_Final.docx 385KB Download
Office_365_Beta_Identity_Service_Description_final.docx 335KB Download
Office_365_Security_Service_Description_Final.docx 550KB


imageOf course, what most folks want is details of the “features and functionality of Office 365 services” to be in the released product.

According to the “Microsoft SharePoint Online Beta Service Description” document, Access Services will be available in the following User Subscriptions:

  • image For Small Businesses SharePoint Online in Plan P1
  • For Information Workers SharePoint Online Plan 2 in E3/E4

Kurt Mackie Described Office 365 Licensing in a Article of 3/26/2011

Office 365 Licensing: Analyst Explains All

Licensing Office 365 was the topic of a Directions on Microsoft talk last week, which may be of interest to IT pros, especially since Microsoft is preparing to launch those services sometime this year.

Availability of Office 365 may be just around the corner. In response to a question during the online session last Thursday, Rob Horwitz, research chair at the Directions on Microsoft consultancy, said that Microsoft intends to deliver Office 365 commercially "before July 2011." However, he noted that Microsoft hasn't publicly announced the start date.

Understanding Office 365 licensing doesn't require a slide rule, an advanced computer science degree or a Microsoft certification, but it probably does require expert advice (and maybe you'll want to keep a lawyer on retainer). During the talk, Horwitz sketched out the major licensing information forks to consider amid a preponderance of choices.

Office 365, like the Business Productivity Online Suite (BPOS) it will succeed, will be offered via monthly recurring subscription fees on a per-user basis. Subscriptions will be available via Microsoft's online subscription program or through enterprise agreements (EAs) with Microsoft. Subscriptions will also be available from Microsoft's partners. The EA route enables better discounts, Horwitz said, and most organizations will likely buy Office 365 through that means. If an organization doesn't have an EA in place, one can be started principally to run Office 365, he added. Office 365 isn't available through Select or Select Plus or open subscription licensing, he explained.

Organizations used to licensing on-premises Microsoft solutions through EAs will have some licensing complications to consider if they migrate to Office 365. For those already using Microsoft's BPOS online services, a helpful Microsoft blog post indicates that current BPOS customers will have a year to opt into Office 365, but those who delay their move won't get all of the benefits of the new suite of services. BPOS users considering moving to Office 365 can get more information at Microsoft's Office 365 transition center page.

Bundled Online Offering
Office 365, when available, will offer a bundle of services based on four of Microsoft's on-premises products. Organizations will get automatic software updates through the service, but Office 365 services currently don't have all of the features offered by the on-premises products. The one standout included in the offering is Office Professional Plus, which is a premises-installed software product. Horwitz said that organizations subscribing to Office 365 would likely be responsible for having to maintain Office Professional Plus themselves, including patching and upgrades.

The four services in Office 365 are as follows:

  • Exchange Online 2010
  • Lync Online 2010
  • SharePoint Online 2010, and
  • Hosted Web Apps

Horwitz noted that the Web Apps, which include Word, Excel, PowerPoint and OneNote, have some limitations when compared with their on-premises cousins. For instance, macros don't work in Excel, he said. Moreover, Office Web Apps can only open documents on a SharePoint site.

Microsoft supports mixed use of on-premises products and services in a hybrid approach. Horwitz said that Exchange Online offers the greatest parity with the on-premises Exchange product. The exceptions include no support for public folders with Exchange Online, plus organizations cannot use Outlook 2003 as a client app for e-mail.

Microsoft's blog post flatly declares that Office 365 does not support "Windows 2003 or earlier, Microsoft Office 2003 and Microsoft Office Outlook 2003." In addition, there is no support for Internet Explorer 6, so those organizations with Web apps built on that browser face some choices if moving to Office 365.

Lync Online has some limitations, Horwitz said. It can't be used for call control of a PBX (private branch exchange). It has limited federation capabilities with non-Microsoft solutions. In addition, users currently can't make or receive calls to or from public switched telephone network (PSTN) users.

SharePoint Online has limited integration with existing business systems, Horwitz explained. It has limited compatibility for scorecards or dashboards, he added.

Licensing Dice and Slice
Office 365 licensees will have about a dozen options from a "dice and slice" menu designed to support small businesses, medium-size businesses and deskless workers (now called "kiosk workers" in Microsoft's licensing parlance), Horwitz explained.

Small business users are defined as having up to 25 users at $6 per user per month. There's no support for more than 50 mailboxes, and no support for conferencing with more than 50 users.

Microsoft has four licensing categories for enterprises (E1 through E4), which are nested "like Russian dolls," with E4 being the most inclusive offering, Horwitz explained. These options include Exchange Online e-mail support for mailboxes of 25 GB in size, personal archiving, calendar and contacts.

The E-1 license includes all Office 365 features at $10 per user per month. The E-2 license adds to that by allowing the editing of documents at $16 per user per month. The E-3 license tops the other two by adding voicemail capability at $24 per user per month. Lastly, the E-4 license adds telephony capabilities at $27 per user per month, such as the ability to make or receive PSTN calls -- although Horwitz said this capability will come later. Even when this capability is available, a "special PSTN number" will be required to make it work, he noted.

The above prices apparently are estimates, and Microsoft could change them by the time it releases Office 365. Microsoft did release its own description of Office 365 pricing that is less detailed than Horwitz's description. Microsoft's pricing list settles on a $24 per user per month price for "organizations who want Office Professional Plus desktop software along with the full functionality of Exchange, SharePoint and Lync Online." This pricing description can be accessed here (Word doc download) from Microsoft's Office 365 home page.

Licensing Overlap
Organizations that already have an EA in place will likely experience "licensing overlap" with Microsoft Office, Horwitz said. Microsoft will allow its EA customers to switch their core Client Access Licenses (CALs) for something called the "Enterprise CAL Suite Bridge for Office 365," which will lower their costs.

The Enterprise CAL Suite Bridge option will only be available to organizations that have an organization-wide EA in place. Microsoft will have the customer sign a contract amendment for the CAL Suite Bridge. This licensing change won't be allowed during the first year. It's not until the next anniversary of the EA, called the "true-up" time, that organizations will be able to get the less expensive CAL Suite Bridge option, Horwitz explained.

Microsoft's licensing is fairly complex, even after an explanation. One possible remedy for further clarification is to attend a Directions on Microsoft event. The consultancy plans to offer its next "Licensing Boot Camp" on April 19 and 20 in Las Vegas, with other dates to follow. The talk by Horwitz can be accessed here.

Notice that there’s no mention of Access Services, Excel Services or InfoPath services in the article.

Tuesday, March 22, 2011

SharePoint 2010 Lists’ OData Content Created by Access Services is Incompatible with ADO.NET Data Services

Updated 3/21/2011 with Pablo Castro’s reply of 3/21/2011 to my thread about the problem in the OData Mailing List (see end of post).

Updated 3/20/2011 with added introductory background material and links to related information.


image Microsoft SharePoint has gained a substantial share of the market for content management and collaboration tools. Sales of SharePoint 2007 exceeded US$1 billion and Mary Jo Foley reported in her What Is Microsoft's Next Billion-Dollar Business? article of 9/1/2010 for Redmond Magazine that “SharePoint is well on its way to becoming Microsoft's first new $2 billion business.”

image SharePoint 2010 is likely to become a data source for a wider range of Microsoft .NET, Windows Phone 7 and other OS client applications because it it exposes list collections in OData format. My Access Web Databases on What is OData and Why Should I Care? post of 3/16/2011 explains the significance of OData-formatted information and how to manipulate it with PowerPivot for Excel.

image Microsoft Access 2010 has the capability to easily and quickly publish conventional *.accdb databases to Web Databases, which run under SharePoint 2010’s Access Services. Access Services stores relational tables in SharePoint lists, displays forms in SharePoint Web pages, and prints reports with the assistance of SQL Server Reporting Services.

image Visual Studio LightSwitch Beta 2 is a rapid application delivery (RAD) framework for SilverLight Windows and Web database clients that targets user and targets developer populations similar to those of Access. LightSwitch accepts OData, SQL Server, and SQL Azure as a data sources. PowerPivot for Excel runs on OData from SharePoint, and OData’s the only data format offered by Microsoft’s Windows Azure Marketplace DataMarket.

image Windows Phone 7 has an OData software development kit (SDK), Android phones can process OData with the Java SDK, and there’s an OData SDK for iPhone’s Object C language. (See J. C. Cimetiere’s OData interoperability with .NET, Java, PHP, iPhone and more post of 3/16/2011 to the Interoperability @ Microsoft blog.) OData is likely to become a leading format in the rapidly growing mobile data market.

Problem Discovery

While running tests with SharePoint 2010’s OData producer as a data source for Visual Studio 2010 and LightSwitch Beta 2 client applications, I encountered the following error when attempting create a Visual Studio LightSwitch Beta 2 Service Reference from an Access application published to SharePoint 2010:

1. I started a LightSwitch project in Visual Studio and selected SharePoint as the Data Source Type:


2. I clicked Next to Enter Connection Information for a SharePoint site created from an Access 2010 project:


The NorthwindTraders site was created by running the Northwind Traders Web Database template from Office Online to create an Access *.accdb database and then publishing it to Access Services in a hosted SharePoint 2010 instance at

3. When I clicked Next, I received the following error message:


The problem relates to the OData client rejection of two leading underscores in the Name property of a column in all lists generated by Access tables. However, the Microsoft SQL Server Data Portability specification for Simple Identifier provides the following specification:

2.2.4 SimpleIdentifier

The SimpleIdentifier attribute specifies an identifier that conforms to the rules for the String data type as specified in [XMLSCHEMA2].

The following is the XML schema definition of the SimpleIdentifier attribute.

<xs:simpleType name="TSimpleIdentifier">
<xs:restriction base="xs:string"/>

The XML Schema Character Range for Char is: 

#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

The preceding specifications don’t appear to me to specify a pattern that precludes two leading underscores.

You can’t edit the column name of a list linked to Access in the SharePoint UI or with SharePoint Designer 2010. The field is hidden by default in Access Datasheet view. You can unhide the field, but Datasheet views of tables linked to SharePoint lists don’t have a Design mode:


To change the __OldID column name to OldID, you must disconnect the Access front-end from the Access Services version to enable modifying the list designs in the UI, edit 15 lists for this example, and then reconnect Office Access to Access Services. This is, to be generous, a daunting task.

After you perform the preceding tasks for the NorthwindTraders example, the Choose Your SharePoint Items dialog appears as expected:


Following is the corrected Product entity displayed in VS LightSwitch Beta 2:


So far, I haven’t found any side effects from removing the two underscores, other than the OldID column now appears by default in Access Datasheet view.

Tests with a simple VS 2010 C# Console application exhibit the same problem.

image It’s interesting that PowerPivot for Excel doesn’t exhibit a similar problem. See the “Browsing OData-formatted Web Database Content in PowerPivot for Excel” section of my Access Web Databases on What is OData and Why Should I Care? post.


The pattern applied to the TSimpleIdentifier Entity Data Model data type that precludes leading underscores should be removed in a later EDM v4.1 CTP because the rule is arbitrary. Changes to Access Services to eliminate the leading underscore and change the method for making columns with such names hidden by default in Access would need to wait for Office Service Pack 2.

Update 3/22/2011 Pablo Castro’s reply of 3/21/2011 to my thread about the problem the OData Mailing List:

Date: Mon, 21 Mar 2011 05:54:35 +0000

image From: Pablo Castro <Pablo.Castro@MICROSOFT.COM>

Subject: Re: ADO.NET Data Services Client Considers Field Names with Leading Underscores Invalid

I pinged the SharePoint folks to see if this is a known issue and whether there are any workarounds. The short story is that there is a mismatch of rules between SharePoint names and EDM names, so the adapter between the two needs to deal with these things. If I hear from them I'll get back to this thread with whatever I learn.


Pablo is a Microsoft Software Architect and OData’s initial Program Manager and Technical Lead. If Pablo replies, I’ll post an update.

Full Disclosure: I’m a contributing editor for Visual Studio Magazine, a sister publication to Redmond Magazine, both published by 1105 Media.

Sunday, March 20, 2011

Access to SQL Server Migration: Access Solutions using SQL Server

Bill Ramos (@billramo) posted Mary Chipman’s (@marychipman) Access to SQL Server Migration: Access Solutions using SQL Server, Part 1 and Access to SQL Server Migration: Access Solutions using SQL Server, Part 2 on 3/19/2011. From Part 1’s introduction:

image In Part 1 and Part 2 I’ll discuss your options for continuing to use Access as a front-end client once you have migrated the data to SQL Server. Some people come to SQL Server migration as Access developers who are new to SQL Server, whereas others may be IT professionals who know little about Access, so I will attempt to bridge any gaps with useful information for everyone. The SSMA Migration Assistant for Access (SSMA) makes it easy to link converted SQL Server tables and queries to the Access database you started from. For applications of any complexity, migrating the data is by far the easiest step. If your existing Access application suffered from intractable problems when the tables were in native Jet/ACE format, and you have done nothing to fix or at least understand those problems, then you are most likely going to have even bigger problems with SQL Server.

image The Access client application has often been dismissed as a "toy" because of its ease of use, but when understood and used appropriately with SQL Server on the back end, those very features can help you quickly deliver cost-effective results with a low TCO. Access is not a suitable client for Web or n-tier applications that require a separate data access layer, although it can be used in conjunction with other clients, such as ASP.NET. There are always tradeoffs involved between ease of development, efficiency and security when using Access in a 2-tier, client-server scenario. You will need to determine which of the following techniques are best suited to your needs.

From Part 2’s introduction:

image In Part 2 I'll continue the discussion about how you can "tread lightly" on your SQL Server by making your Access front end an efficient and economical data consumer. I'll focus on techniques you can use to keep your application running efficiently, freeing up network and server resources in the process.

Mary is an independent consultant, an Access security expert, and a former developer/writer for the Microsoft Access team. She’s co-author of the classic Microsoft Access Developer's Guide to SQL Server.

Friday, March 18, 2011

Upsizing the Northwind Web Database to an Updated SharePoint 2010 Server Hosted by

Updated 3/18/2011 with instructions for correcting time-zone errors starting at Figure 7.

image Chapter 23 of my Microsoft Access 2010 In Depth book, “Sharing Web Databases with SharePoint Server 2010,” includes a “Signing Up for and Testing a Trial Access Hosting Account” section. After the book published, upgraded their shared hosting plan in January 2011 with the following new features:

    • Support for English, Spanish, German, and French language packs on shared hosting plans …
    • Support for the OData service entry point into all Access Web Databases (see my What is OData and Why Should I Care? post of 3/12/2011.)
    • A new and improved control panel for self-service administration of user account passwords
    • Support for permissive handling of all file types including PDF
    • Support for SharePoint Designer outside of Access Web Databases

I was interested in giving SharePoint’s Open Data Protocol (OData) Service a try, so I requested and received an upgrade to my Access Hosting test account. To simplify the initial testing of OData representation of data delivered by SharePoint Server’s Access Services, I downloaded the Northwind Traders Web Database template from Office Online to create a local NorthwindWebDatabase.accdb (NWWDB) Access 2010 database.

NWWDB is an extensively revised version of the classic Northwind.mdb, which has been Access’s sample database file since v1.0’s “Cirrus” beta. To simplify browser-based data entry and editing, NWWDB uses Access 2010’s new Navigation (tab) control to choose data entry pages. For example, here’s a screen capture of the Products List page:

imageFigure 1.

SharePoint lists don’t support relationships, so Category is a lookup field that lets you select from a list populated by the Categories table. Similarly the Supplier lookup field is populated by the Suppliers table.

Clicking the File tab’s Info link opens the Information page:

imageFigure 2.

Clicking the Publish to Access Services button runs the Compatibility Checker and opens the Save & Publish page:

imageFigure 3.

Typing the Server URL ( for the updated shared hosting servers) generates the full URL for uploading to a specific site (

Clicking the Publish to Access Services button connects to your account at AccessHosting’s Website and display the Windows Security dialog:

imageFigure 4.

Typing an administrative password and clicking OK starts the upload process, which displays a progress dialog for each table, form and report:


imageFigure 5.
After a couple of minutes or more, depending on your upload bandwidth, the following success dialog opens:

imageFigure 6.

Click OK to dismiss the dialog, open IE and navigate to the full URL ( for this example) to display the default Dashboard form for entering new orders. (If you didn’t mark the Save My Credentials check box in the login dialog above, you’ll need to log in.)

If you local time zone isn’t Eastern, which is SharePoint’s default and the location of Access Hosting (Delaware), you receive a warning at the top of the screen:


Figure 7.

Click the More Information link, which leads to a generic Fix a Technical Problem page, close the page, click the Options menu, choose Site Permissions to open the Permission Tools ribbon, open the Site Actions menu, and choose Site Settings to open the Site Settings page and click the Site Administration group‘s Regional Setting link:


Figure 8.


Figure 9.
In the Regional Settings page, select your Time Zone from the list:


Figure 10.

Scroll down and click OK to save your change.
Return to the Dashboard and click the Products tab to open SharePoint’s version of Figure 1:

imageFigure 11.

Pasta is obviously the wrong category for Chai (according to Wikipedia, A beverage made with black teas, steamed milk and sweet spices based loosely on Indian recipes), so open the Category field’s lookup list and select Beverages:

imageFigure 12.

Click the selection button of another record in the leftmost column of the grid to save the Category change.

Display NorthwindTraders Content as OData in IE9

Navigate to ( for this example) to display the chosen site’s lists available as OData collections:

imageFigure 13.

Note: The “vti” element of the_vti_bin folder name is an abbreviation for Vermeer Technologies, Inc., the original developers of the FrontPage Web designer for Internet Explorer. Microsoft purchased the FrontPage code in January 1966 and then discontinued the product in 2006 in favor of Microsoft SharePoint Designer and Microsoft Expression Web.

Viewing the contents of collections requires turning off IE9’s Feed Reading view, which is enabled by default. To do this, click the Tools icon, choose Internet Options to open the dialog of the same name, click the Content tab and Feeds and Web Slice Setting button to open the dialog of the same name, and clear the Turn On Feed Reading View check box:

imageFigure 14.

Click OK twice to close the dialogs and save your changes.

Reopen IE and navigate to ( for this example) to display the content of collections exposed by SharePoint 2010. To display a member of the collection by its ordinal, add the number as a suffix enclosed in parentheses ( for this example):

imageFigure 15.

Note: Item names contained in OData query expressions, such as Products in the preceding URL example, are case-sensitive. The Edm type prefix is an abbreviation for Entity Data Model, which describes data types compatible with the ADO.NET Team’s Entity Framework v4.1.

See my What is OData and Why Should I Care? post of 3/12/2011 (updated 3/17/2011) for more information about OData and manipulating OData-encoded lists with Microsoft Power Pivot for Excel 2010.

Wednesday, March 16, 2011

Access Web Databases on What is OData and Why Should I Care?

Updated 3/16/2011 with addition of LightSwitch Beta 2 as an OData consumer.

Updated 3/14/2011 with instructions for logging in to the Northwind Traders demonstration Web Database with public, View Only permission and viewing list/table data with PowerPivot for Excel. See the Browsing OData-formatted Web Database Content in PowerPivot for Excel section below.

One of the data interchange formats for SharePoint lists is the Open Data Protocol. According to Microsoft’s Open Data Protocol (OData) Web site:

imageThe Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications,services, and stores. The protocol emerged from experiences implementing AtomPub clients and servers in a variety of products over the past several years. OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites.

OData is consistent with the way the Web works - it makes a deep commitment to URIs for resource identification and commits to an HTTP-based, uniform interface for interacting with those resources (just like the Web). This commitment to core Web principles allows OData to enable a new level of data integration and interoperability across a broad range of clients, servers,services, and tools.

OData is released under [Microsoft’s] Open Specification Promise to allow anyone to freely interoperate with OData implementations.

OData was known during its beta period as Project “Astoria” and later as ADO.NET Data Services. It’s current name is Windows Communication Framework (WCF) Data Services. OData’s generally accepted as adhering to the Web’s Representational State Transfer (REST) architectural style, which qualifies the protocol as RESTful. You can keep up to date with OData developments by subscribing to MSDN’s  WCF Data Services Team blog.

The OData Web site provides the following lists of application that expose OData services and current live OData services:

imageApplications that can expose OData Services

SharePoint 2010

Any data you've got on SharePoint as of version 2010 can be manipulated via the OData protocol, which makes the SharePoint developer API considerably simpler.

IBM WebSphere

The IBM the WebSphere eXtreme Scale REST data service supports OData.

Microsoft SQL Azure

If you have a SQL Azure database account you can easily expose an OData service through a simple configuration portal. You can select authenticated or anonymous access and expose different OData views according to permissions granted to the specified SQL Azure database user.

Windows Azure Table Storage

Windows Azure Table provides scalable, available, and durable structured storage in the form of tables exposed as OData services.

SQL Server Reporting Services

Microsoft SQL Server 2008 R2 Reporting Services can expose data from reports as OData. [See TechNet’s Generating Data Feeds from Reports (Report Builder 3.0 and SSRS) article, which mentions AtomPub but not OData.]

Microsoft Dynamics CRM 2011

The latest version allows you to query using OData


GeoREST is a web-centric framework for distributing geospatial data. It allows RESTful feature-based access to spatial data sources, including full editing capabilities, through a MapGuide server or directly via FDO.

SDL Tridion 2011

SDL Tridion is a Web Content Management solution, the Content Services component now supports OData

Webnodes CMS

Webnodes CMS is an enterprise quality ASP.NET CMS with a unique semantic content technology. Webnodes recently added OData support. Read more about it here.

Telerik OpenAccess ORM

In mid-2010 Telerik released a LINQ implementation that is simple to use and produces domain models very fast. Built on top of the enterprise-grade Telerik OpenAccess ORM the LINQ implementation allows you to easily build an OData feed via a few easy steps by using the OpenAccess Visual Designer and the Data Services Wizard. For more info, visit

Sitefinity CMS by Telerik

The Sitefinity CMS by Telerik is ready to host OData services. With the powerful API, any developer can expose any information from the CMS through a custom OData service. For more info, visit

Telerik TeamPulse

The Telerik TeamPulse Silverlight client interacts with the database using a WCF data service, and more specifically by using the Open Data Protocol which is a popular way to expose information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites.

The OData protocol comes in extremely handy for TeamPulse, because it exposes the TeamPulse data for digesting and distribution among teams and people, making sure that everyone will find what they need very quickly within the large repository of valuable information in the TeamPulse data store. For more info, visit

Build your own

Using the OData-SDK you can add support for OData to your application.

image Live OData Services

Facebook Insights

An OData Service for consuming Facebook Insights data.



ebay now exposes its catalog via OData



The complete netflix catalog title via OData.  See the Netflix developer OData documentation for more information



twitpic now exposes its Images, Users, Comments etc via OData


Windows Live

You can now use an OData client to talk to your Windows Live resources (Photos, Contacts, Status, etc) whose REST endpoints are now OData endpoints.


Microsoft PDC 2010

Information about all the sessions / speakers etc for Microsoft PDC 2010 exposed via OData



Pluralsight courses are now available via an OData feed


DevExpress Channel

DevExpress has lots of training videos, now available via an OData feed.



A social map of Vancouver Open Data. A collection of data services showing everything from parking lots to drinking fountains.


Vancouver Street Parking

This feed exposes Vancouver street parking information.


Open Government Data Initiative

Open Government Data Initiative (OGDI) is an open source data publishing solution for government agencies.


Open Science Data Initiative

OSDI is based on OGDI which in turn uses the Azure Services Platform to make it easier to publish and use a wide variety of scientific data from government agencies.

Lots of feeds but no service document. You can however use their custom browser.

The City of Edmonton Open Data Catalogue

Public data from the city of Edmonton.


Windows Azure Marketplace DataMarket

Windows Azure Marketplace DataMarket allows producers to sell premier data to consumers, using OData.


TechEd 2010

Microsoft TechEd 2010 conference session data.


Nerd Dinner

Nerd Dinner is a website that helps nerds to meet and talk, not surprisingly it has adopted OData



A community effort to extract structured information from Wikipedia and to make this information available on the Web, with full support for OData interactions on the live query services. (Powered by OpenLink Virtuoso.)

browse or query

Linked Open Data Cloud Cache

Mirrors and interlinks dozens of data sets including all of, with full support for OData interactions. (Powered by OpenLink Virtuoso.)

browse or query

OData Test Service (Read-Only)

This service is specially designed to introduce OData, it has a simple model and only a small number of resources.


OData Test Service (Read-Write)

As above, but this time read-write (with some restrictions).



The famous Northwind Database exposed as an OData Service.


OData Website Data

Data, like producers and consumers, from the OData Website exposed as OData.


Stack Overflow

Q&A for programmers


Super User

Q&A for computer enthusiasts and power users


Server Fault

Q&A for system administrators and IT professionals


Meta Stack Overflow

Q&A about Stack Overflow, Server Fault and Super User


Telerik TV

Telerik's catalog of libraries, videos, Tags and Series

browse ...

Public Transit Data Community

Collection of mass transit data from a variety of transportation agencies across the United States. See developer documentation for more details.

browse ...


Project time tracking software for freelancers and small to medium teams.



INETA Live has an OData feed providing access to their vast library of User Group Presentations.


Microsoft Pinpoint

Microsoft Pinpoint marketplace now exposes its data using OData - more details coming soon



Proagora is a site that allows you to search for jobs, companies, and experts.

browse in English or French

One of the primary applications for OData-formatted information is delivering data to smartphones. Following is a list of OData consumers from the OData Web site with smartphone consumer SDKs emphasized:

imageOData Consumers

Most modern browsers allow you to browse Atom based feeds. Simply point your browser at one of the OData producers.

Visual Studio LightSwitch

VS LightSwitch Beta 2 supports OData from SharePoint 2010 lists, as well as SQL Server and SQL Azure as data sources. Initial tests with Access Web Databases throw an error. I’ll report the status of a fix for the error with an update.

OData Explorer

A Silverlight application that can browse OData Services. It is available as part of the OData SDK Code Samples, and is available online at

Excel 2010

PowerPivot for Excel 2010 is a plugin to Excel 2010 that has OData support built-in.


LINQPad is a tool for building OData queries interactively.

Sesame - OData Browser

A preview version of Fabrice Marguerie's OData Browser.

Client Libraries

Client libraries are programming libraries that make it easy to consume OData services. We already have libraries that target:

For a complete list visit the OData SDK.

OData Helper for WebMatrix

The OData Helper for WebMatrix and ASP.NET Web Pages allows you to easily retrieve and update data from any service that exposes its data using the OData Protocol.


Tableau - an excellent client-side analytics tool - can now consume OData feeds

Telerik RadGrid for ASP.NET Ajax

RadGrid for ASP.NET Ajax supports automatic client-side databinding for OData services, even at remote URLs (through JSONP), where you get automatic binding, paging, filtering and sorting of the data with Telerik Ajax Grid.

Telerik RadControls for Silverlight and WPF

Being built on a naturally rich UI technology, the Telerik Silverlight and WPF controls will display the data in nifty styles and custom-tailored filters. Hierarchy, sorting, filtering, grouping, etc. are performed directly on the service with no extra development effort.

Telerik Reporting

Telerik Reporting can connect and consume an existing OData feed with the help of WCF Data Services.

Database .NET v3

Database .NET v3 - A free, easy-to-use and intuitive database management tool, supports OData

Browsing OData-formatted Web Database Content in PowerPivot for Excel

imageAfter downloading and installing PowerPivot for Excel 2010 from, click the PowerPivot tab to open the PowerPivot ribbon and click the PowerPivot Window Launch button to open its ribbon.

Update 3/14/2011: If you want to run a live test with the NorthwindTraders Web Database site hosted in an Trial account, connect to in a browser. When the Windows Security dialog appears, type AH\devtest1 as the username and access as the password,  and mark the Remember My Credentials check box:


Figure 1.

Click OK to display the OData metadata:


Figure 2.

imageLeave the metadata window open, click the From Data Feeds button to open the Table Import Wizard’s Connect to Data Feed dialog, type or paste the same Data Feed URL, for the demonstration Web Database, and add a Friendly Connection Name, as shown here:

imageFigure 3.

imageClick Next to open the Select Tables and Views dialog, after providing your credentials again, if requested. Mark the check boxes for the Source Tables (lists) you want to include:

image Figure 4.

Click Finish to import the data:


Figure 5.

Click Close to display the contents of the first list in alphabetical order (Categories). Click the tab at the bottom of the page to display the list you want (Products for this example):


Figure 6.

Select the columns that don’t contain interesting information, right click a selected column and choose Hide or Delete to remove it fom the Pivot table, and drag foreign key (lookup) values, such as CategoryID and SupplierID to the left:


Figure 7.

At this point, you can perform all common Excel PivotTable operations on the PowerPivot data.