Deskripsyon
This WordPress plugin allows you to use Microsoft Azure Storage Service to host your media and uploads for your WordPress powered website. Microsoft Azure Storage is an effective way to infinitely scale storage of your site and leverage Azure’s global infrastructure.
For more details on Microsoft Azure Storage, please visit the Microsoft Azure website.
For more details on configuring a Microsoft Azure Storage account and on using the plugin with the Block Editor or Classic Editor, please visit the user guide.
Known Issues
Storage Account Versions
Storage accounts can be created via CLI, classic Azure portal, or the new Azure portal,
with varying results.
If a Storage account is created with the new Azure portal, authentication will fail,
resulting in the inability to view/add containers or files. Creating a Storage account
with the Azure CLI should allow the plugin to work with new Storage accounts.
Responsive Images in WordPress 4.4
Images uploaded to the Azure Storage service will not automatically receive responsive versions.
Images added through the WordPress Media Loader should get automatically converted to responsive
images when inserted into a post or page.
We are investigating options for full support of responsive images in the plugin.
Pag-install
- Upload the plugin files to the
/wp-content/plugins/windows-azure-storagedirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the ‘Plugins’ screen in WordPress.
- Use the Settings->Microsoft Azure screen to configure the plugin.
For multisites or to enforce Azure Blob Storage settings, you can define the following constants in wp-config.php:
- MICROSOFT_AZURE_ACCOUNT_NAME – Account Name
- MICROSOFT_AZURE_ACCOUNT_KEY – Account Primary Access Key
- MICROSOFT_AZURE_CONTAINER – Azure Blob Container
- MICROSOFT_AZURE_CNAME – Domain: must start with http(s)://
- MICROSOFT_AZURE_USE_FOR_DEFAULT_UPLOAD – boolean (default false)
- MICROSOFT_AZURE_OVERRIDE_CONTAINER_PATH – Override Container name in the Image URL , can be just “/”
See Settings->Microsoft Azure for more information.
Mga Review
Mga Contributor at Developer
Ang “Microsoft Azure Storage for WordPress” ay open source software. Ang mga sumusunod na tao ay nag-ambag sa plugin na ito.
Mga Contributor
Ang “Microsoft Azure Storage for WordPress” ay naisalin na sa 1 (na) locale. Salamat sa mga tagasalin para sa kanilang mga kontribusyon.
Isalin ang “Microsoft Azure Storage for WordPress” sa iyong wika.
Interesado sa development?
Tingnan ang code, i-check ang SVN repository, o mag-subscribe sa development log sa pamamagitan ng RSS.
Changelog
4.5.2 – 2025-10-29
- Security: Add capability check when replacing media to prevent privilege escalation by authenticated users (props @peterwilsoncc, @dkotter via GHSA-pwm5-mwxv-fjrh, CVE-2025-10749)
- Security: Bump
minimatchfrom 4.0.7 to 4.0.8 (props @dependabot via #253). - Changed: Bump WordPress “tested up to” version 6.7 (props @mehidi258, @jeffpaul, @dkotter, @hugosolar via #259).
- Changed: Bump WordPress “tested up to” version 6.7 (props @QAharshalkadu, @jeffpaul, @dkotter via #264).
- Developer: Update all third-party actions our workflows rely on to use versions based on specific commit hashes (props @jeffpaul, @dkotter via #262).
- Developer: Updated GitHub Action workflow permissions (props @jeffpaul, @dkotter via #265).
- Developer: Clarified all license references to explicitly reference BSD-2-Clause (props @jeffpaul, @peterwilsoncc via #269).
4.5.1 – 2024-07-17
- Fixed: Fix path issue that duplicates the container name in URL paths (props @hugosolar, @cally423, @Besdima, @ms2oo8, @BCornelissen, @dkotter via #246).
4.5.0 – 2024-07-15
- Added: Feature to replace images at the blob storage level (props @hugosolar, @rickalee, @dkotter via #230).
- Added: Constant for
MICROSOFT_AZURE_OVERRIDE_CONTAINER_PATH(props @rickalee, @engrshakirali, @hugosolar via #240). - Changed: Bump WordPress “tested up to” version 6.6 (props @hugosolar, @jeffpaul via #242).
- Changed: Update WordPress minimum supported version to 6.4 (props @hugosolar, @jeffpaul via #242).
- Removed: Image with special character which isn’t needed anymore (props @hugosolar, @dkotter, @rickalee, @jeffpaul via #234).
- Fixed: Issue with the use of
array_flipand not ensuring it was an actual array (props @hugosolar, @rickalee, @dkotter via #230). - Fixed:
webpcompatibility when uploading original images (props @hugosolar, @rickalee, @ali-awwad via #231). - Fixed: Issue with unchecking year/month option under Settings > Media causes intermediate images not being uploaded to the container (props @hugosolar, @rickalee, @glowmedia via #232).
- Fixed: Media uploader title “Uploading to Azure…” stuck after image is uploaded (props @hugosolar, @rickalee, @eflorea via #233).
- Fixed: Issue with enqueuing admin script in the footer (props @hugosolar, @rickalee via #238).
4.4.2 – 2024-05-06
Note that this release bumps the minimum WordPress version from 5.7 to 6.3.
- Added: New feature to replace PDF files at the blob storage level (props @hugosolar, @rickalee via #220).
- Changed: Bump WordPress “tested up to” version 6.5 (props @QAharshalkadu, @jeffpaul via #223).
- Changed: Bump WordPress minimum from 5.7 to 6.3 (props @QAharshalkadu, @jeffpaul via #223).
- Changed: Replaced lee-dohm/no-response with actions/stale to help with closing no-response/stale issues (props @jeffpaul via #218).
- Fixed: Issue with the transient generated for displaying progress (props @hugosolar, @rickalee via #220).
- Fixed: Ensure we send the proper content type when creating the Block Blob in the container (props @hugosolar, @rickalee, @MWaser, @okadots, @sarahannnicholson, @nicoladj77 via #224).
4.4.1 – 2024-01-08
- Added: Support for the WordPress.org plugin preview (props @dkotter, @jeffpaul via #212).
- Changed: Bump WordPress version “tested up to” 6.4 (props @QAharshalkadu, @jeffpaul via #208, #209).
- Changed: Align our PHP minimum version checks to use new helper method (props @radeno, @ravinderk via #202).
- Fixed: Remove urlencode from srcset calculation function (props @hugosolar, @rickalee, @Sidsector9 via #211).