Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →

Coming soon — in testing, not yet released

Audio Gallery

Audio Gallery turns a SharePoint library, a OneDrive folder or a SharePoint list of tracks into a playlist that plays in the page — built and in testing, not yet released to customers.

Register interest See what is released today

Audio Gallery is built, and is being tested against real tenants before it is released. Nothing on this page can be bought or embedded yet, and what people ask for is what sets the order things are released in.

st-brides.example/talks
st brides
Talks A folder as a playlist
Advent address
  • Michaelmas talk24:10
  • Choral evensong51:38
  • Organ recital18:02
  • Lent series — first reading31:47
  • Bell ringers’ practice12:25

A drawing of Audio Gallery on a fictional site, in our own tokens rather than a customer’s brand. It is a drawing of the arrangement, not a screenshot and not a running widget.

Putting it on the page

The pattern it follows.

Audio Gallery is not released, so there is no embed key to hand out and nothing here to paste yet. It is built on the same script-plus-custom-element pattern as every released component, described below.

There is no embed snippet yet

Embed keys are issued when a component is released, and this one has not been. The three parts beside this note are the pattern it already shares with the released components.

  1. The script tag

    One bundle for one component. It defines the custom element and does nothing else — no framework, no build step, and no change to how the rest of the page is built.

  2. The element

    An ordinary HTML tag, placed wherever the component should appear — including inside a page builder’s raw-HTML block, a shortcode, or a template partial.

  3. The embed key

    The key resolves to one configured instance — the Microsoft 365 source, the arrangement, the theme, and the domains allowed to render it. Change any of those and the page itself never has to be edited again.

What it does

How it works

The Audio Gallery component reads audio files from a SharePoint document library, a OneDrive folder, or a SharePoint list where each row is a track, and renders them as a playlist with a player in the page. Publishing an episode means adding a file. It is built and in testing, and has not been released to customers.

Why it exists

Audio on a website is usually a column of file links, which is a download prompt rather than something anyone listens to. The recordings already sit in a shared folder; what is missing is a player that treats that folder as a playlist.

Element
<wpi-audio-gallery>
Reads from
SharePoint document libraries, OneDrive for Business, SharePoint lists
Arrangements
4 in the builder
Graph access
managed or proxy — the tenant chooses

Where it runs

Anywhere you can paste two lines of HTML

A custom element needs no build step and no framework, so where your site is built is not a question you have to answer before this one.

  • WordPress
  • Webflow
  • Squarespace
  • Shopify
  • Wix
  • Astro
  • Next.js
  • Drupal
  • SharePoint pages
  • Plain HTML

Named as examples of places HTML can be pasted. No partnership is implied and none of these are customers. WordPress is the one that gets more than an embed — the same Microsoft 365 jobs also ship as plugins with a Gutenberg block.

In detail

Everything Audio Gallery does.

7 capabilities, every one of them resolved from the embed key rather than written into the page — once the keys are issued.

  1. A folder becomes a playlist

    A SharePoint document library or a OneDrive folder, either of which can read the subfolders below it, or a SharePoint list whose columns carry the title, artist, album, audio file, artwork, duration, category and order for each track.

  2. Four views, three player styles

    A track list, cards one to three columns wide, a compact arrangement, or a single track. The player itself is a bar, a card or a minimal control — and it can stay pinned to the viewport while the visitor scrolls the rest of the page.

  3. Playback you decide the shape of

    Loop the playlist, shuffle it, offer playback-rate control, draw a waveform, and choose how much of each file the browser fetches before play — metadata being enough to show durations. Autoplay is a setting, and the builder says plainly that browsers still gate it behind a gesture.

  4. Track details from the file itself

    Title, artist and duration come from the file’s own audio metadata for library and folder sources, and from mapped columns for a list. Artwork, artist, album, duration and track numbers are each switchable, with a default artwork image for tracks that have none.

  5. Search, filter, sort and page

    Sort by name, artist, created date, modified date, duration or a manual order; add a search box and a category filter; and show up to 500 tracks at once or split them into pages of up to 200.

  6. Downloads as a decision, not a default

    Downloads are off unless you turn them on, so a talk can be listenable in the page without being distributable from it. The file types served are MP3, M4A, AAC, WAV, OGG and FLAC by default, and the list is yours to narrow.

  7. The platform settings every component gets

    Domain allowlist, a Google Tag Manager container id, the shared theme tokens, custom CSS, and the same script-plus-custom-element embed pattern as the released components.

Tell us you are waiting on this one.

Audio Gallery is in testing and no release date is announced. What people ask for is what sets the order things are released in, so a sentence about your case is worth more here than a waiting list.

Register interest

Reaching your tenant

Two ways for us to reach Graph. One of them never lets us.

Every tenant runs in one mode or the other, and the choice belongs to your IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.

managed

We hold the credentials

WPIntegrate runs the client-credentials flow for your tenant. Your administrator grants consent once and is not asked again.

proxy

You hold the credentials

You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.

Arrangements

The arrangements it offers

Each of these is a setting on the instance, not a different component — the source, the theme and the embed key stay the same when you change it.

  • Track list
  • Cards — one to three columns
  • Compact
  • Single track

Questions

What people ask about this one.

If yours is not here, ask it — the answers come back from a person rather than a form.

Can we use Audio Gallery yet?

Not yet. It is built and is being exercised against real tenants by our own team, and it has not been released to customers — so it cannot be created in a customer dashboard or embedded on a site.

Where does the audio come from?

Microsoft 365: a SharePoint document library, a OneDrive folder, or a SharePoint list with one row per track. Library and folder sources read the file’s own audio metadata; a list maps its columns instead.

Do listeners need a Microsoft account?

No. Access is resolved server-side with the tenant’s own Graph credentials, the same way the released components do it, so a visitor presses play without signing in to Microsoft.

Can listeners download the files?

Only if you switch downloads on. They are off by default.