Merge pull request #15947 from MicrosoftDocs/main

Publish main to live 10/31/2024, 3:30 PM

Teams/answer-auto-attendant-and-call-queue-calls.md

@@ -5,10 +5,10 @@ author: mkbond007
 ms.author: mabond
 manager: pamgreen
 audience: ITPro
-ms.date: 08/01/2023
+ms.date: 10/31/2024
 ms.topic: conceptual
 ms.service: msteams
-description: Describes Cloud Auto attendants and Call queues, and explains how you can answer these calls in Teams.
+description: Describes Cloud Auto attendants and Call queues, and explains how you can answer these calls in Microsoft Teams.
 f1.keywords:
 - NOCSH
 ms.localizationpriority: medium
@@ -35,41 +35,41 @@ Cloud Call queues include greetings that are used when someone calls in to a pho
 
 ## Handling an Auto attendant or Call queue call
 
-Users will be able to differentiate incoming calls from an Auto attendant or Call queue before they answer the call. Along with the name and/or number of the caller, each call will include the display name of the resource account assigned to the Auto attendant or the Call queue that the caller was trying to reach, giving users a better context for addressing the caller.
+Users can differentiate incoming calls from an Auto attendant or Call queue before they answer the call. Along with the name and/or number of the caller, each call includes the display name of the resource account assigned to the Auto attendant or the Call queue that the caller was trying to reach, giving users better context for addressing the caller.
 
-The following illustration shows how an incoming call from an Auto attendant or Call queue will appear to a user.
+The following illustration shows how an incoming call from an Auto attendant or Call queue appears to a user.
 
 ![Screenshot of an incoming call notification.](media/answer-auto-attendant-and-call-queue-calls-image1.png)
 
-Once an Auto attendant or Call queue call is answered, the user can process the call like any other call — they can add or conference in another user or transfer the call to another party. Also, Auto attendant calls will be forwarded based on the user's configuration.
+Once an Auto attendant or Call queue call is answered, the user can process the call like any other call — they can add or conference in another user or transfer the call to another party. Also, Auto attendant calls are forwarded based on the user's configuration.
 
-> [!NOTE] 
-> Call queue calls are not forwarded based on the user's call answering rules configuration. This is to ensure callers remain in the queue until an agent can answer the call and the caller isn't forwarded unexpectedly.
+> [!NOTE]
+> Call queue calls aren't forwarded based on the user's call answering rules configuration. This ensures that callers remain in the queue until an agent can answer the call and that the caller isn't forwarded unexpectedly.
 >
-> Users receiving calls from Call queues will only be presented with the name of the caller if it's provided from the PSTN or if the caller's number matches the target user's local Team's client contacts.
+> Users receiving calls from Call queues are only presented with the name of the caller if it's provided from the Public Switched Telephone Network (PSTN) or if the caller's number matches the target user's local Teams client contacts.
 >
-> Agents are not notified of any missed calls or voicemails for Call queue calls.
+> Agents aren't notified of any missed calls or voicemails for Call queue calls.
 
 ## Supported clients
 
 Support for Auto attendant and Call queue calls is available in the following clients:
 
-- Microsoft Teams Windows client (32 and 64-bit versions)
+- Microsoft Teams Windows client (32-bit and 64-bit versions)
 - Microsoft Teams Mac client
 - Microsoft Teams iPhone app
 - Microsoft Teams Android app
 
-The Teams client is only supported with a [co-existence mode of Teams Only](/microsoftteams/setting-your-coexistence-and-upgrade-settings).
+The Teams client is only supported with a [coexistence mode of Teams Only](/microsoftteams/setting-your-coexistence-and-upgrade-settings).
 
 ## Configure Auto attendant and Call queue support for Microsoft Teams
 
-To receive Auto attendant and Call queue calls on Microsoft Teams, you need to configure your interoperability policy and upgrade policy. Please review [Migration and interoperability for organizations using Teams together with Skype for Business](migration-interop-guidance-for-teams-with-skype.md). If you do not have Auto attendant and/or Call queue configured and would like to do so, see [Set up a Cloud Auto attendant](create-a-phone-system-auto-attendant.md) and [Create a Cloud Call queue](create-a-phone-system-call-queue.md).
+To receive Auto attendant and Call queue calls on Microsoft Teams, you need to configure your interoperability policy and upgrade policy. For more information, review [Migration and interoperability for organizations using Teams together with Skype for Business](migration-interop-guidance-for-teams-with-skype.md). If you don't have Auto attendants and/or Call queues configured and would like to do so, see [Set up a Cloud Auto attendant](create-a-phone-system-auto-attendant.md) and [Create a Cloud Call queue](create-a-phone-system-call-queue.md).
 
 ## Known Issues
 
-When a Call queue agent receives a call on their mobile device, the call may go on hold if the device is locked. Users must unlock the device first and then answer the call.
+When a Call queue agent receives a call on their mobile device, the call might go on hold if the device is locked. Users must unlock the device first and then answer the call.
 
-## Related topics
+## Related articles
 
 [Create a Cloud Call queue](create-a-phone-system-call-queue.md)
 

Teams/app-ownership-developer-portal.md

@@ -0,0 +1,78 @@
+---
+title: Ownership of apps in Developer Portal
+author: ashishguptaiitb
+ms.author: guptaashish
+manager: prkosh
+ms.topic: article
+ms.service: msteams
+audience: admin
+ms.subservice: teams-apps
+ms.date: 10/21/2024
+ms.collection: 
+- Teams_ITAdmin_Help
+- M365-collaboration
+search.appverid: 
+f1keywords: 
+description: 
+appliesto: 
+- Microsoft Teams
+ms.localizationpriority: medium
+---
+
+# Manage Microsoft Teams app ownership in Developer Portal
+
+App developers use [Developer Portal](/microsoftteams/platform/concepts/build-and-test/teams-developer-portal) to configure, distribute, and manage their Teams apps. Developers who create or import an app in Developer Portal becomes the owner of the app. An app owner can add other org users as owners as well.
+
+An owner may leave the organization or can delete the app from the portal after the app is published. In such cases, a Global Administrator can help in the following ways:
+
+* Take over the ownership of an app and add other developers as owners.
+* Import the app if it was created outside of Developer Portal or was deleted from the portal.
+
+The above tasks help admins to let another developer work on the app and manage it, hence maintaining business continuity.
+
+## Admin takes ownership of a custom app
+
+Your organization can use a custom app that is available just within your org and not on the Teams store. It's created for and managed within your org.
+Admins can take ownership of a custom app in the following scenarios:
+
+* Custom app that is available in the portal.
+* Custom app that wasn't created in or is removed from the portal.
+
+### Take ownership of custom app available in the portal
+
+If a custom app exists in the portal, then taking ownership isn't possible for a user. Admins can either import the zip archive or take ownership in the following ways.
+
+| Role | Available option | Outcome on app ownership |
+|------|------------------|--------------------------|
+| Admin | Import > Replace | Recommended approach if you have the app zip archive. Retains app ID of previous app so the app remains the same. The portal overwrites ownership making you the sole owner. You can add new org users as owners. |
+| Admin | Take ownership | Recommended approach if you know the app ID. The portal adds you as yet another app owner. You can add other users as developers. |
+| Admin | Import > Replace | Creates a new app ID and makes the admin as owner. No relation to the previous app. |
+| User | Import | Creates a new app ID so no relation to the previous app. Uploader is the owner and can add other developers. |
+
+> [!TIP]
+> To know the app ID, use the app details page in the Teams admin center. If the app is deleted from admin center, then import the zip archive of the app.
+
+### Take ownership of custom app not available in the portal
+
+It is possible to create a custom app without using the Developer Portal or to delete it after creation. In this case, your org doesn't have the app available in the portal. You can import or take ownership in the following ways.
+
+| Role | Available option | Outcome on app ownership |
+|------|------------------|--------------------------|
+| Admin | Import | Provide app ID in the import dialog. The portal makes you the sole owner and you can add other users as owners. There's no impact on the app as it doesn't exist in the portal. |
+| Admin | Take ownership | If app was created in the portal, admin can provide app ID and take ownership as the sole owner. It doesn't work if app was created outside the portal. |
+| User | - | Not possible for a user to either import or to take ownership. |
+
+## Admin takes ownership of a Store app
+
+An org can publish its app to [Microsoft AppStore](https://appsource.microsoft.com) using Partner Center UI.
+
+In the above cases, you as an admin can reclaim the ownership of the app in Developer Portal by contacting Microsoft Support. To ascertain the ownership, provide the following details to Microsoft Support:
+
+* Proof of ownership of the app: Provide a screenshot of the email approval from Microsoft app validation team. When an org submits a Teams app in Partner Center, Microsoft validates the app and contacts from `[email protected]` email ID. Microsoft app validation team lets your org know that the app is approved for publishing to the AppStore.
+* Your tenant ID.
+* Your app's ID.
+
+## Related articles
+
+* [Know about Developer Portal](/microsoftteams/platform/concepts/build-and-test/teams-developer-portal).
+* [Developer Portal Teams app](https://teams.microsoft.com/l/app/14072831-8a2a-4f76-9294-057bf0b42a68).

Teams/call-sharing-and-group-call-pickup.md

@@ -4,7 +4,7 @@ author: mkbond007
 ms.author: mabond
 manager: pamgreen
 ms.date: 12/12/2023
-ms.reviewer: jenstr
+ms.reviewer: jastark
 ms.topic: article
 ms.tgt.pltfrm: cloud
 ms.service: msteams
@@ -42,9 +42,12 @@ Users must be assigned a Microsoft Teams Phone license to set up and use call sh
 
 ## Limitations
 
-A user can only be the owner of one call group. Each configured call group can have a maximum of 25 users or 32,768 characters. A user can be a member of maximum 25 call groups.
+- A user can only own one call group.
+- Each call group can have up to 25 users.
+- A user can be a member of up to 25 call groups.
+- If you add more than five members to a call group, the ring order automatically switches to "Everyone at once."
 
-Note that mobile devices will only get notified if they're set for banner and ringtone.
+Mobile devices are only notified if they're set for banner and ringtone.
 
 ## Enable the use of group call pickup
 
@@ -69,7 +72,7 @@ To configure immediate call forward settings:
 
 1. Select **Manage call group** and select **Add people** to add the appropriate users to the call group.
 
-1. For each user in the call group, select the type of notification that the user will see when they get an incoming call. **Ring** is the default notification type.
+1. For each user in the call group, select the type of notification that you want the user to see when they get an incoming call. **Ring** is the default notification type.
 
 1. From the dropdown, select the appropriate call group order.
 

Teams/considerations-calling-plan.md

@@ -28,13 +28,13 @@ description: "Learn about emergency calling considerations for Microsoft Calling
 
 This article describes emergency calling considerations for Microsoft Calling Plan users. Before reading this article, see emergency calling concepts and definitions in [Plan and manage emergency calling](what-are-emergency-locations-addresses-and-call-routing.md).
 
-To find out if Microsoft Calling Plans are the right solution for your business, see [PSTN connectivity options](pstn-connectivity.md) and [Microsoft Calling Plans for Teams](calling-plans-for-office-365.md).
+To find out if Microsoft Calling Plans are the right solution for your business, see [Public Switched Telephone Network (PSTN) connectivity options](pstn-connectivity.md) and [Microsoft Calling Plans for Teams](calling-plans-for-office-365.md).
 
 ## Emergency call enablement for Calling Plans
 
 Each Calling Plan user is automatically enabled for emergency calling and is required to have a registered emergency address associated with their assigned telephone number.
 
-When the location is associated to the telephone number depends on the country/region:
+The point in time when the location is associated to the telephone number depends on the country/region:
 
 - In the United States and Canada, an emergency location is required when a number is assigned to a user.
 
@@ -48,7 +48,7 @@ Dynamic location for routing emergency calls is supported in the United States a
 
 - If a Teams client for a United States Calling Plan user dynamically acquires an emergency address within the United States, that address is used for emergency routing instead of the registered address. The call is automatically routed to the PSAP in the serving area of the address.
 
-- If a Teams client for a United States Calling Plan user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP.
+- If a Teams client for a United States Calling Plan user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones and Microsoft Teams Rooms route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP.
 
 Dynamic location for routing emergency calls is supported in Canada the same as in the United States with the following exception: all emergency calls are screened nationally before being transferred to the PSAP.
 
@@ -70,7 +70,7 @@ For example:
 
 - If a Teams client is located at a tenant-defined dynamic emergency location, emergency calls from that client are automatically routed to the PSAP serving that geographic location.
 
-- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location.
+- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone or Microsoft Teams Room, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location.
 
 - If an emergency caller is unable to update their emergency location to the screening center, the call is transferred to the PSAP serving the caller's registered address.