page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
Microsoft Teams app localization using Bot and Tab |
|
|
|
officedev-microsoft-teams-samples-app-localization-csharp |
This sample illustrates how to implement Localization for Microsoft Teams apps.
- Bots
- Tabs
- Localization
Please find below demo manifest which is deployed on Microsoft Azure and you can try it yourself by uploading the app package (.zip file link below) to your teams and/or as a personal app. (Sideloading must be enabled for your tenant; see steps here.).
App Localization: Manifest
Verify you have the right account for building Teams apps and install some recommended development tools.
- You need a Teams account that allows custom app sideloading.
- .NET Core SDK version 6.0
- ngrok or equivalent tunnelling solution
-
Register a new application in the Azure Active Directory – App Registrations portal.
NOTE: When you create your app registration, you will create an App ID and App password (Secret) - make sure you keep these for later.
-
Setup for Bot
- Also, register a bot with Azure Bot Service, following the instructions here
- Ensure that you've enabled the Teams Channel
- While registering the bot, use
https://<your_ngrok_url>/api/messages
as the messaging endpoint.
-
Setup NGROK
- Run ngrok - point to port 3978
ngrok http 3978 --host-header="localhost:3978"
-
Setup for code
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
Modify the
/appsettings.json
and fill in the following details: -
{{MicrosoftAppId}}
- Generated from Step 1 while doing AAd app registration in Azure portal. -
{{ClientSecret}}
- Generated from Step 1, also referred to as Client secret -
Run the bot from a terminal or from Visual Studio:
- If you are using Visual Studio
- Launch Visual Studio
- File -> Open -> Project/Solution
- Navigate to
app-localization\csharp
folder - Select
Localization.csproj
file
- This step is related to Microsoft Teams app manifest
- Edit the
manifest.json
contained in theManifest
orManifest_hub
folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string<<YOUR-MICROSOFT-APP-ID>>
and <> and for the contentUrl "<<1234.ngrok-free.app>>?culture={locale}" (depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) - Provide ngrok Url (turnnelling Url) in
manifest.json
for contentUrl in case of tabs and for messaging endpoint in case of bots if enabled. - Zip up the contents of the
Manifest
orManifest_hub
folder to create amanifest.zip
- Upload the
manifest.zip
to Teams (in the Apps view click "Upload a custom app")
- Edit the
Note: If you want to test your app across multi hub like: Outlook/Office.com, please update the manifest.json
in the /Manifest_Hub
folder with the required values.
Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.
In Teams, Once the app is successfully installed, you can interact with tab and bot in your preferred language.
To change the language in Microsoft Teams, please click your profile picture at the top of the app, then select Settings -> General and go to the Language section. Choose the preferred language and restart to apply the change. This sample supports en-US, fr-CA, hi-IN and es-MX.
-
To view your app in Outlook on the web.
-
Go to Outlook on the weband sign in using your dev tenant account.
On the side bar, select More Apps. Your sideloaded app title appears among your installed apps
Select your app icon to launch and preview your app running in Outlook on the web
Note: Similarly, you can test your application in the Outlook desktop app as well.
-
To preview your app running in Office on the web.
-
Log into office.com with test tenant credentials
Select the Apps icon on the side bar. Your sideloaded app title appears among your installed apps
Select your app icon to launch your app in Office on the web
Note: Similarly, you can test your application in the Office 365 desktop app as well.
Add Resource files for the respective languages, Check culture fallback behaviour and how to add other cultures refer Globalization and localization Fundamentals.