Accessing, sharing, and managing documents and media within Microsoft Teams Free
There is no new endpoint documented for downloading legacy Skype AMS attachments after the Skype-to-Teams migration. Attachments referenced by AMS Object IDs continue to be served from the same Skype/Bot Framework attachment service endpoints and require valid authentication.
The only supported, documented way to retrieve historical Skype files now is via the Skype data export flow:
- Go to the Skype Export page and sign in with the same Microsoft account used in Skype.
- Request an export including Files (and Conversations if needed).
- When the export is ready, download the
.tararchive from Available Exports. - Extract the
.tarfile (for example, on Windows 10/11 usingtar -xvf YOURFILENAME_export.tarin Command Prompt) to access the exported media.
If the file is not present in the exported media, or AMS endpoints return Unauthorized, there is no supported alternative endpoint to retrieve that attachment.
For Azure bots used in Omnichannel scenarios, AMS attachments can still be downloaded using the documented Bot Framework attachment endpoint pattern with a valid bot token, but this applies only to Azure bot/Omnichannel integrations, not to consumer Skype history:
string requestUri = $"https://botapi.skype.com/amer/v3/attachments/{attachmentId}/views/original";
var httpRequest = new HttpRequestMessage(HttpMethod.Get, requestUri);
var authorization = new AuthenticationHeaderValue("bearer", <botToken>);
httpRequest.Headers.Authorization = authorization;
httpRequest.Headers.Add("BotAcsId", activity.Recipient.Id);
HttpResponseMessage response = await client.SendAsync(httpRequest);
If AMS returns Unauthorized and the file is also missing from the official export, the attachment is no longer retrievable via supported APIs.
References: