<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Architecture principle/model for limits of user access?</title><link>http://blogs.technet.com/mhatch/archive/2006/10/21/architecture-principle-model-for-limits-of-user-access.aspx</link><description>Reflecting on a funcional review this week where the Operations GM kept talking about business intelligence and 'back-end SQL access' in the same breath, I realized that there needs to be a way to articulate what services users should be allowed to access.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Architecture principle/model for limits of user access?</title><link>http://blogs.technet.com/mhatch/archive/2006/10/21/architecture-principle-model-for-limits-of-user-access.aspx#2564990</link><pubDate>Mon, 26 Nov 2007 17:25:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2564990</guid><dc:creator>Architecture principle/model for limits of user access?</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://feeds.maxblog.eu/item_1392146.html"&gt;http://feeds.maxblog.eu/item_1392146.html&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>