Skype consumer is no longer available for a new NDI podcast setup. Microsoft retired Skype on 5 May 2025, so the former Skype for Content Creators workflow is now historical rather than a set of steps you can follow today.
For a current setup, Microsoft points Skype users towards Teams Free, while NDI documents an NDI output workflow for the new Teams client on Windows. The important limitation is that the available documentation does not confirm that this feature is available to every Teams Free consumer account.
Skype consumer NDI is now a legacy workflow
The old idea was straightforward: bring a remote guest into Skype, expose the call as NDI audio and video, then select those NDI sources in production software such as OBS Studio, Streamlabs or vMix. The production application could then combine the guest with your microphone, graphics, music and camera before sending the programme to YouTube.
That workflow mattered to podcasters because it avoided treating the guest's call window as the final programme output. NDI could provide separate network sources for production, giving you more control over layouts, audio mixing and recording. NDI describes its technology as an IP-based way for software and devices to send and receive audio and video over a network, not as a podcast application by itself. You can read the underlying explanation in NDI's guide to what NDI is.
The distinction matters now. You may still find old tutorials that describe Skype menus, Skype for Content Creators or a Skype NDI setting. Those pages can explain how the former workflow operated, but they do not make consumer Skype available for a fresh installation. Do not spend an evening trying to reproduce an interface that Microsoft has retired.
Microsoft's own Skype retirement notice gives 5 May 2025 as the consumer retirement date. Microsoft's Lifecycle record displays 6 May 2025 in Pacific Time, reflecting the time-zone presentation of the retirement record rather than a different current workflow.
What changed after Skype consumer retired
Microsoft announced that it was moving its free consumer communications focus to Microsoft Teams. That does not mean that every former Skype feature moved across unchanged. A calling service may continue, while a particular production feature, desktop setting or account entitlement differs.
For a podcast, the practical change is that the first question is no longer “which Skype NDI setting should I enable?” It is “does the calling product and account I have support NDI output today?” That question should be answered before you buy accessories, rebuild your scene collection or promise a guest a particular remote-production arrangement.
The old Skype workflow also had a different operating assumption. Many tutorials treated the calling application and NDI output as if they were permanent parts of a creator's toolkit. They are not. Software changes, account types are treated differently, and a setting documented for a work or education tenant may not be present in a personal account.
If your final destination is a long-running YouTube channel rather than a one-off podcast, keep the calling workflow separate from the channel workflow. A guest call is a live production input. It is not automatically a reliable 24/7 broadcast source. For a channel built around recorded episodes, you may want to turn the finished programme into a scheduled or continuous stream after recording. The practical choices are different from keeping a live guest call open overnight, as the discussion in how to make a YouTube stream survive an internet outage illustrates.
Skype for Business is a separate product
Skype for Business should not be used as evidence that consumer Skype remains available. It is a separate Microsoft product with different administration, licensing and deployment contexts. The consumer retirement notice does not turn the two products into one application, and a menu found in Skype for Business does not prove that a personal Skype account can use the same feature.
This is a common source of confusion in search results. A guide may use “Skype” in its title while describing an enterprise product, an archived consumer build or a third-party plugin. Before following it, check which application name appears in the instructions, which account type is required and whether the page describes a current release.
For a small podcast team, Skype for Business is not a sensible substitute simply because the name looks familiar. It may be relevant to an organisation that already operates the product, but that is a separate decision involving the organisation's Microsoft environment. It does not restore the retired consumer Skype for Content Creators workflow.
The same care applies to production software. NDI's creator material names OBS Studio, Streamlabs and vMix as integrations, but the receiving application, plugin and version still need to be checked together. A source appearing in an NDI list does not guarantee that your exact desktop installation will discover it or expose every audio channel in the way you expect.
What NDI contributes to a podcast setup
NDI is a transport and discovery method for audio and video over a network. In a typical podcast arrangement, the calling application creates one or more NDI sources, the production computer discovers them, and the production application adds them to a scene or mixer. The final programme can then be recorded or sent to YouTube using the encoder path you choose.
That is different from sending a Skype or Teams window directly to YouTube. A window capture records whatever is visible, including notifications, controls and changes in the call layout. An NDI source can be more useful when you need to position a guest separately from your host, route the guest's audio independently or switch between scenes without cropping the whole desktop.
NDI does not remove the need for a suitable network. The source and receiving computer must have a network path that allows the media to travel between them. A wired Ethernet connection can be a sensible choice for a fixed studio because it reduces dependence on a busy wireless link, but a new cable is not automatically required for every setup. The correct choice depends on the computers, access point, network layout and the amount of media being carried.
NDI Tools is software rather than a required hardware purchase. The official NDI Tools installation guide directs you to NDI's own site and the installer for your operating system. The official download page listed version 6.3.2 when checked on 3 October 2026; that version can change, so check the page again before installing.
NDI's content-creation page describes support for formats up to 4K at 60 frames per second in 10-bit HDR. Treat that as the vendor's format description, not as a performance result for your computer or network. A podcast using modest camera resolutions may be easier to operate than a production attempting high-resolution, high-frame-rate sources alongside several other devices.
The documented Teams NDI path on Windows
NDI's current instructions describe NDI output for the new Microsoft Teams client on Windows. They are the relevant modern documentation to examine if you are replacing the retired consumer Skype workflow, but they do not by themselves establish that every Teams account can use the feature.
The documented sequence has three parts:
- Install the additional NDI files required by the Teams workflow.
- Enable NDI in Teams' App Permissions.
- During the call, enable Broadcast over NDI.
The first step concerns the computer, not the guest. Install the required software from the official NDI source and use the Windows installer that matches the current documentation. Avoid downloading a random “NDI for Skype” package from an old tutorial or an unofficial mirror. If the software is no longer maintained, you may end up troubleshooting a missing source when the actual problem is that the workflow has been retired.
The second and third steps are separate deliberately. A global permission can allow NDI features in the application, while the call-level broadcast switch determines whether the current call is being exposed as NDI. Turning on a permission does not necessarily mean that every call is broadcasting.
After enabling the feature, open the receiver on the same network and look for the Teams NDI source. The exact source names and available channels can depend on the current application behaviour and account configuration. Add the source to OBS Studio, Streamlabs or vMix only after the receiving application can see it.
Do not treat discovery as proof of production readiness. Check the guest's picture, speech intelligibility, channel routing and delay. Make a short local recording before you publish a live episode. If the guest's audio reaches the scene but is doubled, muted or routed through the wrong monitor device, correct that before connecting the YouTube output.
YouTube is a separate destination. The NDI source feeds your production application; the production application then sends the finished programme through its YouTube encoder or streaming connection. If you are building a recorded library rather than broadcasting the call immediately, record the programme first and review it before turning it into a longer-running channel stream. That separation also makes it easier to manage a long ambient stream with audio that stays in sync.
Enable permissions before the call, then test the call output
Use a short test call for the first setup. Do not make the first attempt during a guest's scheduled appearance, particularly if the guest is joining from a phone or a different time zone.
Start with the Windows computer that will run the production application. Confirm that the new Teams client is installed, that the NDI files required by the documented workflow are present, and that the computer can reach the same local network as the receiving application. If your production computer and calling computer are different machines, both sides need a network path that permits discovery and media traffic.
In Teams, enable the NDI permission described in the current NDI instructions. Then join a test call and look for the call-level option to broadcast over NDI. If that option is absent, stop there rather than assuming that an obscure keyboard shortcut or an old Skype setting will fix it. The missing option may indicate an account limitation, a changed application version or a feature that is not available in your Teams configuration.
On the receiving computer, open the chosen production software and add the available NDI source. Confirm four things independently:
- The guest's video is visible and has the expected framing.
- The guest's voice reaches the intended mixer channel.
- Your own microphone is not returning through the guest source and creating an echo.
- The programme remains understandable when both people speak.
Use headphones for the guest and host where possible. Echo can be introduced before NDI, inside the production mixer or by monitoring the final programme back into the call. Muting a source in one place may not mute it everywhere, so trace the signal from the caller to the NDI source, then through the production mixer and monitoring output.
A wired network is worth considering when the studio computer is stationary and the wireless connection is busy. It is not a magic repair for a weak internet connection to YouTube, an overloaded computer or a guest's unstable connection. Test the whole path: guest to Teams, Teams to NDI, NDI to the production software, and production software to YouTube.
If you are using a recorded video loop around your live segments, keep the file playback and live-call scene separate. A tool that is suitable for looping a video on YouTube Live with VLC is solving a different problem from bringing a live guest into an NDI scene. Mixing those roles without a clear fallback can leave you with neither a clean interview nor a dependable filler programme.
What the documentation does not confirm about Teams Free
Microsoft directed consumer Skype users towards Microsoft Teams Free, but the NDI instructions found for the new Teams client on Windows do not confirm that the NDI broadcast feature is available to Teams Free consumer accounts in every case.
That gap should remain visible in your planning. Do not read “Teams” in an NDI document as “every Teams Free account”. The documentation may be written for a different account category, and feature availability can depend on the client, tenant or current Microsoft policy.
Before committing to a guest workflow, sign in with the actual account you intend to use and check whether the NDI permission and the call-level Broadcast over NDI control are present. If you administer a work or education account, check the relevant Microsoft and NDI documentation for that environment. If you use a personal Teams Free account, treat eligibility as something to verify rather than something this article can guarantee.
This is also why a test with a different Microsoft account is not conclusive. A feature visible to one account may not appear to another, even when both people use the same Windows version. Record the account type, Teams client state and date of your test so that you can repeat the check after an update.
If NDI is unavailable, the alternatives should be assessed honestly. A window capture may be enough for an occasional interview, although it offers less control. A supported calling platform with a documented production integration may suit a team that needs separate guest sources. A local recording from the guest can produce better control over editing, but it is no longer a live remote conversation. There is no reason to force an NDI design when the account cannot provide the source.
For a channel operator who wants the finished podcast to continue running after the live production is complete, a cloud workflow can remove the need to leave the studio computer switched on for the later broadcast. StreamNeo removes that particular handover by letting you upload the finished file, provide the YouTube stream key and leave the channel running while your own computer is off; it does not change whether Teams or NDI can supply a live guest during recording.
A practical decision check before you build the scene
Use the following checks in order. They prevent you from solving a network problem before confirming that the source exists.
| Check | What to confirm | If it fails |
|---|---|---|
| Calling service | You are not depending on retired consumer Skype | Move to a currently supported calling product |
| Account eligibility | Your Teams account actually shows the NDI controls | Verify the account type with current Microsoft or NDI documentation |
| Operating system | The documented Teams NDI path applies to your Windows client | Do not assume the same steps apply to another desktop system |
| NDI installation | The required NDI files are installed from the official source | Reinstall from the current NDI instructions |
| Permission | NDI is enabled in Teams App Permissions | Check the client and account before changing production software |
| Call control | Broadcast over NDI is enabled during the call | Treat the feature as unavailable until confirmed |
| Receiver | Your production application sees the source | Check network discovery and receiver compatibility |
| Audio | Voice is routed once, without echo or unwanted monitoring | Trace the signal through the mixer and headphones |
| Final output | A short recording or private test reaches the intended destination | Fix the production path before inviting a live audience |
A good test is small enough to repeat. Use one host, one guest, one camera source and one production scene first. Add lower thirds, music, remote co-hosts and backup scenes only after the basic source is stable.
Keep a fallback that does not depend on the same failing component. If the guest's NDI source disappears, you might record the conversation locally, switch to a prepared programme, or postpone the live episode. A fallback should be tested in advance, not merely written in a notebook.
The old Skype tutorials cannot provide that certainty because the consumer application itself has retired. Current documentation, account verification and a short rehearsal are more useful than a detailed archived menu path.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I still create a new Skype NDI stream for a podcast?
No. Consumer Skype was retired in May 2025, so you should not plan a new setup around its former NDI workflow. Old tutorials can explain the historical arrangement, but they do not restore the retired service.
Is Skype for Business the replacement for consumer Skype NDI?
No. Skype for Business is a separate product with its own account and administration context. Its documentation or settings should not be used as proof that consumer Skype is still available.
Does Teams Free definitely support NDI output?
The available NDI documentation describes the workflow for the new Teams client on Windows, but it does not confirm that the feature is available to every Teams Free consumer account. Sign in with the account you will actually use and verify that both the NDI permission and Broadcast over NDI control are present.
Do I need a capture card for NDI podcast production?
Not for the NDI connection itself. NDI Tools and compatible production software can receive network audio and video without making a capture card a required part of this workflow, although your wider studio may have separate hardware needs.