<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2025-08-01-preview on Radius Docs</title><link>https://edge.docs.radapp.io/reference/resources/radius.storage/2025-08-01-preview/</link><description>Recent content in 2025-08-01-preview on Radius Docs</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://edge.docs.radapp.io/reference/resources/radius.storage/2025-08-01-preview/index.xml" rel="self" type="application/rss+xml"/><item><title>Radius.Storage/objectStorage@2025-08-01-preview</title><link>https://edge.docs.radapp.io/reference/resources/radius.storage/2025-08-01-preview/objectstorage/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://edge.docs.radapp.io/reference/resources/radius.storage/2025-08-01-preview/objectstorage/</guid><description>&lt;h2 id="description"&gt;Description&lt;/h2&gt;
&lt;p&gt;The Radius.Storage/objectStorage Resource Type deploys an object storage
container (an S3-style bucket / Azure Blob container / GCS bucket). To deploy
one, add an objectStorage resource to the application definition Bicep file.
Unlike database types, no secret is required from the developer: Azure Storage
generates its own account keys, so the platform-engineer recipe needs no
injected credentials.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bicep" data-lang="bicep"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;resource&lt;/span&gt; store &lt;span style="color:#e6db74"&gt;&amp;#39;Radius.Storage/objectStorage@2025-08-01-preview&amp;#39;&lt;/span&gt; = {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; name: &lt;span style="color:#e6db74"&gt;&amp;#39;store&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; properties: {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; environment: environment
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; application: myApplication.id
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; containerName: &lt;span style="color:#e6db74"&gt;&amp;#39;data&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To connect your container to the store, create a connection from the
Container resource to the store as shown below. This verification test is
provisioning-only because the stock demo image has no Azure Blob backend, but
the type still exposes a connection surface for applications that can use it.&lt;/p&gt;</description></item></channel></rss>