Turn conversations into code with GitHub Copilot in Microsoft Teams
Coding where context lives and collaboration happens The best prompt may be the conversation your team has already had or is currently having. Until now, using a coding agent often meant paying context and coordination taxes. Developers had to leave the discussion, open another tool, and reconstruct the problem in a lengthy prompt: what happened, what the team decided, which constraints matter, and what needs to be built. With GitHub Copilot in Teams, teams can move directly from conversation to action. @mention GitHub Copilot when the team is ready to act, and it can use the conversation alongside repository context to understand the request, implement the change, and create a pull request for review. This makes working with a coding agent more collaborative and visible. Instead of one developer privately reconstructing the request, teammates can contribute context, correct assumptions, refine the approach in real time, and review the resulting work together. Let’s explore the new GitHub Copilot in Teams experience to see how it can streamline development tasks: If the player doesn’t load, open the video in a new window: Open video GitHub Copilot in Teams is available in Teams channels, group chats, meeting chats, and 1:1 chats. Once the GitHub app is installed and added to the conversation, @-mention GitHub Copilot to bring it into the discussion and start a task. During public preview, users can complete the following scenarios with GitHub Copilot in Teams: Build a feature based on requirements discussed in Teams Implement a fix for a bug Expand test coverage or improve documentation Create and update a pull request No copying the discussion into a CLI. No rewriting it in a desktop app. No asking one developer to translate a team decision into the perfect prompt. GitHub Copilot works where the context already lives, and because that context is shared, working with GitHub Copilot becomes a team activity. Built around the controls teams already use GitHub Copilot in Teams works within existing GitHub permissions and repository policies. Branch protections and required reviews continue to apply, and people remain responsible for deciding what gets merged, ensuring that humans stay in the loop at every step. Availability GitHub Copilot in Teams is now available in Public Preview. To try it, install the GitHub app for Microsoft Teams and check out our documentation to get started! Less context reconstruction. More progress from the conversations already happening.
Automation for a real estate brokerage
I manage a real estate brokerage and am looking for help in how to utilize Microsoft teams better. I would like to have it automate processes for my associates. Example, they are looking to list a property, it will guide them to a tutorial and provide all of the documents that i uploaded. Another example, they want to request a lockbox or signs, it will ask them the relevant information and then put it in my queue. Any help would be appreciated!
New Diagnostic: Copilot Agent Functionality in Microsoft Teams.
As Microsoft Copilot for Microsoft 365 continues to evolve, ensuring reliable agent performance within Microsoft Teams is critical to delivering a seamless user experience. To support this, we’re introducing the Copilot Agent Functionality Diagnostic—a powerful tool designed to identify and resolve issues that may prevent Copilot agents from operating in Teams. This includes validating eligibility, confirming service availability, and checking for configuration compliance. With this test, organizations can quickly verify that their environment is optimized for Copilot agents, helping users fully leverage the capabilities of Copilot within Teams. Why This Matters For Copilot agents to function seamlessly in Microsoft Teams, several dependencies must be in place—including user authentication, valid license assignment, tenant app settings, and the ability to run required custom apps in preview. If any of these prerequisites are misconfigured, users may face errors, limited functionality, or even lose access to Copilot features altogether. That’s where our Diagnostics comes in -The Copilot Agent Functionality Test helps eliminate these risks by proactively checking authentication, confirming license validity, validating Teams app configurations, and identifying settings that could block Copilot agents. By addressing these issues early, organizations can ensure users experience the full value of Copilot in Teams without disruption. What the Diagnostic Does The Copilot Agent Functionality Diagnostic is designed to help both customers and support engineers validate the critical requirements that enable Copilot agents to work seamlessly in Microsoft Teams. It performs a series of checks to confirm: Successful retrieval of Teams user authentication information Verification that users hold a valid Microsoft 365 Copilot license for Teams Confirmation that custom apps in preview are enabled to support Copilot agents Validation of Teams tenant app settings for proper permissions and availability Identification of configuration gaps that may block agent functionality By running these validations, the diagnostic ensures that the Teams environment is properly configured, reducing the likelihood of errors and empowering organizations to deliver a consistent Copilot experience in Microsoft Teams. Who Should Use It? Note: A Global Administrator account is required to run this diagnostic. IT Admins validating Teams settings, app configurations, and license prerequisites to ensure Copilot agents function correctly. Support Engineers troubleshooting Copilot agent issues related to authentication, configuration, or feature availability. Adoption & Change Management Leads confirming the Teams environment is properly prepared for users to engage with Copilot agents during rollout. Get Started To run the diagnostic, you’ll need a Global Administrator account. To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select COPILOT, then click on the “Copilot Agent Functionality in Microsoft Teams”. A Big Thank you to Rui Andre Tabares.
Agents SDK Teams Bot crashes MSFT.Agents.Core.ProtocolJsonSerializer..cctor() with CLR (0x80131506)
Teams Bot running off Azure Functions .NET 8 (isolated) crashes at Microsoft.Agents.Core.Serialization.ProtocolJsonSerializer..cctor() with Fatal error. Internal CLR error (0x80131506) when initializing Microsoft.Agents.Storage.Blobs Hi team — I’m setting up context storage for a Teams bot using the Microsoft Agents SDK. When the message handler function executes, testing via adding the bot to a meeting chat, DI constructs BlobsStorage, the Functions worker process crashes with a fatal CLR error originating from the Agents serialization bootstrap. My issue seems related to these two issues: https://github.com/microsoft/Agents/issues/224 https://github.com/microsoft/Agents-for-net/issues/386 I have tried the recommended fix of pinning my installed packages to version 1.1.151, and I still encounter this error. csproj: <PackageReference Include="AdaptiveCards.Templating" Version="2.0.5" /> <PackageReference Include="Azure.AI.OpenAI" Version="2.2.0-beta.5" /> <PackageReference Include="Azure.Data.Tables" Version="12.11.0" /> <PackageReference Include="Microsoft.Agents.Builder.Dialogs" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Core" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Storage.Blobs" Version="1.1.151" /> <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="2.0.0" /> <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="2.0.5" /> <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="2.0.2" /> <PackageReference Include="Microsoft.Agents.Authentication.Msal" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Hosting.AspNetCore" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Client" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Connector" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Storage" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Storage.Transcript" Version="1.1.151" /> <PackageReference Include="Microsoft.Bot.Builder" Version="4.23.0" /> <PackageReference Include="Microsoft.Graph" Version="5.91.0" /> <PackageReference Include="Microsoft.Agents.Builder" Version="1.1.151" /> <PackageReference Include="Microsoft.Agents.Extensions.Teams" Version="1.1.151" /> <!-- Exclude TeamsFx wwwroot static files which are for frontend only. --> <!-- Fix system package downgrade --> <PackageReference Include="Microsoft.NETCore.Targets" Version="5.0.0" PrivateAssets="All" /> <PackageReference Include="Microsoft.TeamsFx" Version="3.0.0" /> <PackageReference Include="Newtonsoft.Json" Version="13.0.3" /> My full stack trace is below: Microsoft.Agents.Core.dll!Microsoft.Agents.Core.Serialization.SerializationInitAttribute.InitSerialization() Unknown Microsoft.Agents.Core.dll!Microsoft.Agents.Core.Serialization.ProtocolJsonSerializer.ProtocolJsonSerializer() Unknown [Native to Managed Transition] [Managed to Native Transition] Microsoft.Agents.Core.dll!Microsoft.Agents.Core.Serialization.ProtocolJsonSerializer.SerializationOptions.get() Unknown Microsoft.Agents.Storage.Blobs.dll!Microsoft.Agents.Storage.Blobs.BlobsStorage.BlobsStorage() Unknown [Native to Managed Transition] [Managed to Native Transition] Microsoft.Agents.Storage.Blobs.dll!Microsoft.Agents.Storage.Blobs.BlobsStorage.BlobsStorage(System.Uri blobContainerUri, Azure.Core.TokenCredential tokenCredential, Azure.Storage.StorageTransferOptions storageTransferOptions, Azure.Storage.Blobs.BlobClientOptions options, System.Text.Json.JsonSerializerOptions jsonSerializerOptions) Unknown > MrMinute.dll!Program.<Main>$.AnonymousMethod__0_1(System.IServiceProvider sp) Line 47 C# Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(Microsoft.Extensions.DependencyInjection.ServiceLookup.FactoryCallSite factoryCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSiteMain(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSite(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite constructorCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSiteMain(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSite(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite constructorCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSiteMain(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite transientCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext context) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext, object>.VisitCallSite(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.RuntimeResolverContext argument) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceCallSite callSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope scope) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.RealizeService.AnonymousMethod__0(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope scope) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceIdentifier serviceIdentifier, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope serviceProviderEngineScope) Unknown Microsoft.Extensions.DependencyInjection.dll!Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(System.Type serviceType) Unknown Microsoft.Extensions.DependencyInjection.Abstractions.dll!Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorInfoEx.GetService(System.IServiceProvider serviceProvider, int parameterIndex) Unknown Microsoft.Extensions.DependencyInjection.Abstractions.dll!Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorMatcher.CreateInstance(System.IServiceProvider provider) Unknown Microsoft.Extensions.DependencyInjection.Abstractions.dll!Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance(System.IServiceProvider provider, System.Type instanceType, object[] parameters) Unknown Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Azure.Functions.Worker.DefaultFunctionActivator.CreateInstance(System.Type instanceType, Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown MrMinute.dll!TeamsToDynamics.DirectFunctionExecutor.ExecuteAsync(Microsoft.Azure.Functions.Worker.FunctionContext context) Line 104 C# Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Azure.Functions.Worker.Pipeline.FunctionExecutionMiddleware.Invoke(Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Extensions.Hosting.MiddlewareWorkerApplicationBuilderExtensions.UseFunctionExecutionMiddleware.AnonymousMethod__1_2(Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Azure.Functions.Worker.OutputBindings.OutputBindingsMiddleware.Invoke(Microsoft.Azure.Functions.Worker.FunctionContext context, Microsoft.Azure.Functions.Worker.Middleware.FunctionExecutionDelegate next) Unknown Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Extensions.Hosting.MiddlewareWorkerApplicationBuilderExtensions.UseOutputBindingsMiddleware.AnonymousMethod__3(Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.Invoke(Microsoft.Azure.Functions.Worker.FunctionContext context, Microsoft.Azure.Functions.Worker.Middleware.FunctionExecutionDelegate next) Unknown [Resuming Async Method] System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.<Invoke>d__5>.ExecutionContextCallback(object s) Unknown System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.<Invoke>d__5>.MoveNext(System.Threading.Thread threadPoolThread) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.<Invoke>d__5>.MoveNext() Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.TaskAwaiter.OutputWaitEtwEvents.AnonymousMethod__12_0(System.Action innerContinuation, System.Threading.Tasks.Task innerTask) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action action, bool allowInlining) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task.RunContinuations(object continuationObject) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<Microsoft.AspNetCore.Http.HttpContext>.SetResult(Microsoft.AspNetCore.Http.HttpContext result) Unknown [Completed] Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.SetFunctionContextAsync(string invocationId, Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.__Canon>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.<SetFunctionContextAsync>d__7>.ExecutionContextCallback(object s) Unknown System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<Microsoft.AspNetCore.Http.HttpContext>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.<SetFunctionContextAsync>d__7>.MoveNext(System.Threading.Thread threadPoolThread) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.__Canon>.AsyncStateMachineBox<Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.<SetFunctionContextAsync>d__7>.MoveNext() Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.TaskAwaiter.OutputWaitEtwEvents.AnonymousMethod__12_0(System.Action innerContinuation, System.Threading.Tasks.Task innerTask) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action action, bool allowInlining) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task.RunContinuations(object continuationObject) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task<bool>.TrySetResult(bool result) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task.CancellationPromise<bool>.System.Threading.Tasks.ITaskCompletionAction.Invoke(System.Threading.Tasks.Task completingTask) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task.RunContinuations(object continuationObject) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.Task<bool>.TrySetResult(bool result) Unknown System.Private.CoreLib.dll!System.Threading.Tasks.TaskCompletionSource<bool>.SetResult(bool result) Unknown Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.ContextReference.InvokeFunctionAsync() Unknown Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.RunFunctionInvocationAsync(string invocationId) Unknown Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.AspNetCore.Http.FunctionsHttpContextExtensions.InvokeFunctionAsync(Microsoft.AspNetCore.Http.HttpContext context) Unknown Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.dll!Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.WorkerRequestServicesMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext context) Unknown Microsoft.AspNetCore.HostFiltering.dll!Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware.Invoke(Microsoft.AspNetCore.Http.HttpContext context) Unknown Microsoft.AspNetCore.Server.Kestrel.Core.dll!Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests<Microsoft.AspNetCore.Hosting.HostingApplication.Context>(Microsoft.AspNetCore.Hosting.Server.IHttpApplication<Microsoft.AspNetCore.Hosting.HostingApplication.Context> application) Unknown [Resuming Async Method] System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequests>d__238<Microsoft.AspNetCore.Hosting.HostingApplication.Context>>.ExecutionContextCallback(object s) Unknown System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread threadPoolThread, System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequests>d__238<Microsoft.AspNetCore.Hosting.HostingApplication.Context>>.MoveNext(System.Threading.Thread threadPoolThread) Unknown System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequests>d__238<System.__Canon>>.ExecuteFromThreadPool(System.Threading.Thread threadPoolThread) Unknown System.Private.CoreLib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch() Unknown System.Private.CoreLib.dll!System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Unknown [Async Call Stack] [Async] Microsoft.Azure.Functions.Worker.Core.dll!Microsoft.Azure.Functions.Worker.FunctionsApplication.InvokeFunctionAsync(Microsoft.Azure.Functions.Worker.FunctionContext context) Unknown [Async] Microsoft.Azure.Functions.Worker.Grpc.dll!Microsoft.Azure.Functions.Worker.Handlers.InvocationHandler.InvokeAsync(Microsoft.Azure.Functions.Worker.Grpc.Messages.InvocationRequest request) Unknown [Async] Microsoft.Azure.Functions.Worker.Grpc.dll!Microsoft.Azure.Functions.Worker.GrpcWorker.ProcessRequestCoreAsync(Microsoft.Azure.Functions.Worker.Grpc.Messages.StreamingMessage request) Unknown [Async] System.Private.CoreLib.dll!System.Threading.Tasks.Task.Run Unknown Thank you in advance for the assistance
Masking MS Teams Service Desk Agents
Hello, I would like my Service Desk agents to be more active answering questions in MS Teams, but what I would like to try and avoid are staff trying to contact those agents directly after the fact. Does anyone know of a way where I can mask a group of MS Teams users in specific channels so that the name of the user is masked (ie shows Helpdesk instead of John Smith). Thx!
