teams
1117 TopicsAssistance on Microsoft Townhalls, Live events and Webinars
Dear All, We hope you're enjoying our new Teams Town Halls! To further support your event experience, we’re excited to introduce the Microsoft Live Event Assistance Program (LEAP)—a complimentary service designed to help you seamlessly plan and execute your events (New Teams Townhalls, Live events, Webinars) What Does LEAP Offer? This free program connects you with Microsoft event experts who can assist with: Training and demos Configuration support Assistance before, during, and after your Town Halls, webinars, or live events Whether you're transitioning from Teams Live Events to Town Halls or planning future events, our team is here to guide you every step of the way. How to Access Free Support To receive assistance for your Microsoft events, simply log a support case with our experts. Please bookmark or update the following links to submit your request: Microsoft events assist portal (LEAP) Microsoft free support for your events (LEAP) Important Notes for First-Time Users Profile Creation: On your first visit, you may be prompted to create a profile. If redirected to a form that doesn’t mention LEAP, simply revisit Live Event Assist after profile creation. When submitting your support request, please follow these guidelines: Product Family: Cloud and Online Services Product: Live Events Assistance Program (LEAP) Support Type: Professional No Charge Issue Description: Title: Live Events Assistance Request Event Date and Duration Event Location Note: Use your work contact details (corporate email). Personal accounts such as Outlook or Gmail are not supported. If you're an event attendee, please contact your event host for assistance. Additionally, our team can assist with Microsoft eCDN-related queries. Learn More To explore the full benefits of the LEAP program, visit: Microsoft Virtual Event Guidance We look forward to helping you make your events a success!149Views0likes0CommentsMeeting Options are limited
Hello, I have run into a problem of not having a full access to meeting options. I would like to schedule meetings for other people in the office where I do not necessarily have to attend. I would also like to assign other people as co-hosts so that they are able to admit people and have more control of the meeting. There should be settings of being able to let people come in without waiting in the waiting room as well, but I cannot seem to find it anywhere. Here is the attached screenshot: These are the only two options I get when clicking "Meeting Options". Additionally, whenever I set up a meeting, some people are not able to respond to it because they get an error of undeliverable response: "delivery has failed to these recipients or groups". What is the issue here? Does it have to do with how Outlook is set up? How can I change these limitations and errors? Thank you so much!18Views0likes0CommentsTeams Room System Autopilot deployment does not work - Error Code: 6, 0x80180014
Problem: We are attempting to deploy our Microsoft Teams Room (MTR) systems, some of which are already in use, using Windows Autopilot in self-deploying mode. Despite following the official guide, we keep encountering errors. https://learn.microsoft.com/en-us/microsoftteams/rooms/autopilot-autologin Procedure: Device: Certified Intel NUC, previously in use. Installation: Windows 11 Pro installed. Autopilot Import: Device imported into Autopilot. Group Assignment: GroupTag "MTR-ConsoleName" assigned. Dynamic Group: Device appeared in the Dynamic MTR group. Assignments: Deployment Profile and ESP (Enrollment Status Page) assigned. Teams Room Update App: Deployed via Intune, assigned to the MTR group, and integrated into the ESP. LAPS: Local Administrator Password Solution (LAPS) is active. Teams Rooms Pro Console: Device appeared and was assigned to a resource account with a Teams Room Pro license. Error Description: After the setup process, we consistently encounter an error during device registration for mobile management: Error Code: 6, 0x80180014 Attempts to resolve the issue: Deleted the device completely from Intune and Autopilot and re-added it. Created a custom Device Restriction Policy to allow all devices in the group. Additionally, during one attempt where the error did not occur, Teams failed to set up automatically. Questions: Why does error 6, 0x80180014 occur during device registration for mobile management? Are there specific requirements or settings beyond the official guide that need to be considered? What steps can be taken to ensure that Teams sets up automatically when the registration error does not occur? Objective: We aim to ensure that the MTR systems are smoothly deployed via Autopilot in self-deploying mode and that Teams sets up automatically. Thank you for your support!Teams Room System Autopilot deployment does not work - Error Code: 6, 0x801800141.1KViews0likes4CommentsFor sharing screen
Hi to all, during metting (on desktop app) when sharing the screen, the shared scrceen slowly pixelate to gray to participants. At the end all screen is gray. This happen also with my desktop app (version 25017.203.3370.1174.) Anyone else has thi problem? Thanks Andrea82Views0likes10CommentsUnread chat in teams first
Good day All, Our company just moved to Teams and we have a few groups in Teams (Channels) and we miss messages due to Teams does not allow Unread messages from channesl first, How could i change that when a message comes it goes to the top? It does this in the normal chat but not in the Teams Channels? Please advise.4KViews0likes3CommentsYou don't have access to this org in Teams.Select another org, or contcat your admin
This user is within my organisation and not a guest but when she tries to open Teams we get You don't have access to this org in Teams.Select another org, or contcat your admin She was a member of another org in MS Teams previously using the same email address as her organisational one. We logged onto account.activedirectory.windowsazure.com and deleted the other org but a) teams still remembers it and b) we still can't log on to the actual organisation she is a member of Help!211KViews1like37CommentsCSS Properties being stripped from Teams Chat messages from Bot
Hi Team, We've noticed that certain CSS properties are no longer appearing in HTML messages when sent to Teams Chat. Previously, our bot styled messages using display and border properties, but now these properties are missing from the HTML when we inspect the page. Steps to Reproduce: Start the Echo bot from the sample templates (I used Teams Toolkit to deploy it to Teams or run it in the Test tool). In the TeamsBot.ts file, modify the onMessage function by replacing await context.sendActivity(...) with the following code. This example adds styling to an echo message. const a: Partial<Activity> = { text: `<span style="display: block; color: red; border-radius: 4px; padding: 4px; border: 1px solid red; ">Echoo:</span> <span style="display: block;">${txt}</span>`, textFormat: TextFormatTypes.Xml }; await context.sendActivity(a); Note: I also tried sending the HTML directly with context.sendActivity(...) without setting the textFormat property in the Activity, and observed the same result. Run the bot in the Test tool and Teams to compare behavior. Observed behavior: In the Test tool: All styles are applied as expected. In Teams: Only the color property is applied, while display, padding, and border properties are ignored (stripped out of the HTML). Here’s an example of the HTML output in Teams: <div dir="auto" id="content-1730973548675" aria-label="Echoo: test styles properties" class="fui-Primitive ___16zla5h f1oy3dpc fqtknz5 fyvcxda"> <span style="color: red;">Echoo:</span> <span>test styles properties</span> </div> Could you provide insights on whether this change is intended, and if there are any workarounds for preserving these CSS properties in Teams messages? Thank you!481Views11likes3CommentsHow to resolve "Failed to submit this app" error?
Hi Team, Just from Today, while submitting teams custom app via Developer Portal, error "Failed to submit this app." started to occur. I have tried with below condition but this error always occurs. Error also occurs on the app which we can submit update till yesterday. What is happening and how can we resolve it? (from this error message, we couldn't guess anything about the reason..) Checked: ・Publish from outside Developer Portal (apps > manage apps > send app to organization) succeeded so seems Developer Portal related Issue. ・For all apps, no validation error in "Publish to store" is found. Manifest itself seems to be fine. ・Create new custom app with minimum configuration and publish but failed with same error. ・Tried publish from both Teams client and Browser but failed with same error. ・Try same operation with different tenant but failed with same error.13KViews0likes26CommentsApp icons disappear when you switch tenants
Since the most recent version of Teams was released, when I switch tenants (away from my home tenant, to another tenant in my multi-tenant organisation), I found that all the app icons have vanished from the sidebar. Every time I want to use an app, I have to go through the process of adding it to Teams. However, although this lets me use an app during the current session, the icon never appears in the sidebar (next time I switch, I have to add the app again in order to use it). Same problem is happening to other users in my organisation too - we've not changed any settings. Both the Windows app, and browser versions are affected, although not the iOS app (so far). Anyone else had this?26Views0likes0Comments