M365.TeamsBackup

Check out my blog posts regarding the tool:

Usage

Add the account to all teams to backup. Ensure he has access to all private channels or private channels will not be backedup

Run executable with parameter for the environment "--environment Production"

I tested the setup as a Global Administrator and you should also use a Global Admin to setup.

You can setup the application via the includes scripts:

Using Azure AD PowerShell module (manuel admin consent)
- .\deploy\create-aadapp.ps1
- Change the name of the app to your liking ($appName)
Using Azure CLI (including admin consent)
- .\deploy\create-aadapp-cli.ps1
- Change the name of the app to your liking ($appName)

Or for a manuel setup through the Azure portal:

Name: e.g. dev-GKMM-msteamsbackup-app
Supported account types: My organization only
Authentication
- Add mobile and desktop
- Advanced Settings
  - Allow public client flows: Yes
API Permission
- MS Graph
  - Delegate
    - Channel.ReadBasic.All
    - ChannelMember.Read.All
    - ChannelMessage.Read.All
    - ChannelSettings.Read.All
    - Group.Read.All
    - GroupMember.Read.All
    - Team.ReadBasic.All
    - TeamMember.Read.All
    - TeamSettings.Read.All
    - TeamsTab.Read.All
- Grant admion consent for ORG

appsettings(.Development|.Production).json

M365
AzureAd
- Instance: Should be https://login.microsoftonline.com in most cases
- ClientId: Azure AD App Id from your tenant. The app uses the device code flow only at the moment
- TenantId: Your tenant ID required for the audience
- Scope (string array): Most of the time https://graph.microsoft.com/.default is good enough
Backup
- Path: Output directory for the JSON files
- JsonWriteIndented: Use pretty (easy to read) JSON with formating. Setting to "false" will save some space.
- TeamId: Optional. If filled only this team will be used for backup

appsettings.(Development|Production).json