sdk
54 TopicsWindows Admin Center SDK is now generally available
First published on on Sep 20, 2018 We’re excited to announce the GA release of the Windows Admin Center SDK! Windows Admin Center has been designed with extensibility in mind from the beginning, and with our SDK, you can integrate your own functionality into Windows Admin Center.14KViews0likes0CommentsUnlock the Potential of AI in Your Apps with Semantic Kernel: A Lightweight SDK for LLMs
Semantic Kernel (SK) is a lightweight SDK enabling integration of AI Large Language Models (LLMs) with conventional programming languages. The SK extensible programming model combines natural language semantic functions, traditional code native functions, and embeddings-based memory unlocking new potential and adding value to applications with AI. SK supports prompt templating, function chaining, vectorized memory, and intelligent planning capabilities out of the box11KViews2likes0CommentsThe Future of AI: Computer Use Agents Have Arrived
Discover the groundbreaking advancements in AI with Computer Use Agents (CUAs). In this blog, Marco Casalaina shares how to use the Responses API from Azure OpenAI Service, showcasing how CUAs can launch apps, navigate websites, and reason through tasks. Learn how CUAs utilize multimodal models for computer vision and AI frameworks to enhance automation. Explore the differences between CUAs and traditional Robotic Process Automation (RPA), and understand how CUAs can complement RPA systems. Dive into the future of automation and see how CUAs are set to revolutionize the way we interact with technology.10KViews6likes0CommentsWe’ve made updates to the Windows Admin Center SDK (Preview)!
First published on on Aug 09, 2018 We’re excited to announce the following updates to the SDK, currently in public preview: Windows Admin Center CLI Target an SDK version Refreshed examples Publishing extensions and plugins What’s next?Windows Admin Center CLIWe’ve released the Windows Admin Center CLI as part of the SDK! The CLI installs seamlessly alongside your other global dependencies by running ‘npm install -g windows-admin-center-cli’.10KViews0likes0CommentsScale your data sharing needs with the power of Azure Data Share’s .NET SDK
Azure Data Share, now a generally available service, makes it very simple to share your organization’s data securely with your partners. You may have already seen and tried it on the Azure Portal to share data swiftly, without writing any code. But what if you want to scale your sharing needs to thousands of customers spread across the world? Data Share offers a rich API/SDK for you to leverage and scale your sharing relationships seamlessly. Let’s jump right in and walk through a sample use case using the .NET SDK.9KViews2likes0CommentsWindows Admin Center SDK - Public Preview Release
First published on on May 03, 2018 Ever since the Technical Preview release of Windows Admin Center (previously Project Honolulu) at Ignite last year, partners and customers have been asking how to integrate with Windows Admin Center.8.7KViews0likes1CommentGet Microsoft Teams transcript api or sdk
Hi - does anyone know if Microsoft Teams has an API to retrieve a meeting transcript after the meeting has ended or if the teams SDK allows it? I haven't been able to find an API or a way to do it through the SDK, but just wanted to make sure in case I overlooked something. Thanks!Solved6.8KViews2likes4CommentsIgnite 2024: Streamlining AI Development with an Enhanced User Interface, Accessibility, and Learning Experiences in Azure AI Foundry portal
Announcing Azure AI Foundry, a unified platform that simplifies AI development and management. The platform portal (formerly Azure AI Studio) features a revamped user interface, enhanced model catalog, new management center, improved accessibility and learning, making it easier than ever for Developers and IT Admins to design, customize, and manage AI apps and agents efficiently.5.9KViews2likes0CommentsCalling resources on Trusted Application API for Skype Business Online shows CallbackUriUnreachable
I am tasked with implementing a bot connector for Skype for Business Online, and to say it has been challenging is an understatement. I realize that the Trusted Application API is very new, and just for fun, I also work in a PHP shop, so I'm really not doing myself any favors. However the beauty of a REST api is supposedly that the language I choose to implement in doesn't matter. In any case, I have jumped through the many hoops of Azure AD authentication and have gotten a reliable process built for getting a token and retrieving the top-level resource urls. But, when I call these resources (which should be the last step before seeing "hello" in my skype client) I am stymied by an error. I am calling my "startMessaging" resource, as defined by the communication group on the main Application resource request. Example call going to https://api.skypeforbusiness.com/platformservice/v1/applications/3168576520/communication/messagingInvitations?endpointId=sip:joanbot@equityim.onmicrosoft.com sends this data in the body: { "to":"sip:awaschick@equityim.onmicrosoft.com", "operationId":"1", "callbackUrl": "https://janedev8001.ngrok.io/event" } In response, I get: { "code": "BadRequest", "subcode": "CallbackUriUnreachable", "message": "Exception of type 'PlatformService.Web.ValidationException' was thrown.", "debugInfo": { "errorReportId": "7ade7fb108cd4d28b5ecfebafe6e86bc" } } The thing is, on my dev proxy, it never registers an incoming request at my specified callback URL. It's there, I can hit it myself, so everybody else should be as well. When I configured my Skype endpoint as instructed by the trusted api documentation, in Powershell, though, I get back this information: RunspaceId : e62a1040-160f-4d5f-a186-d114b76992e2 FriendlyName : jane-dev Id : 458ff1f0-53b3-495b-b0ce-47d1cbad5849 TenantId : e39d3de2-8d8c-4285-a31d-b4144c3d82d8 EndpointType : Targeted SipUri : sip:joanbot@equityim.onmicrosoft.com PhoneNumber : CallbackUri : Ring : ClientAudience : No default callback Uri. I'm wondering, is this the callback endpoint that it can't reach when I try to start messaging? I'm at a loss here as to how to define this, if so. I can't find documentation on a specific cmdlet I can run that will let me set this value, if so. I'm quite at the end of my rope here. What am I missing? Andy5.1KViews0likes26Comments