Truth in IT
    • Sign In
    • Register
        • Videos
        • Channels
        • Pages
        • Galleries
        • News
        • Events
        • All
Truth in IT Truth in IT
  • Data Management ▼
    • Converged Infrastructure
    • DevOps
    • Networking
    • Storage
    • Virtualization
  • Cybersecurity ▼
    • Application Security
    • Backup & Recovery
    • Data Security
    • Identity & Access Management (IAM)
    • Zero Trust
    • Compliance & GRC
    • Endpoint Security
  • Cloud ▼
    • Hybrid Cloud
    • Private Cloud
    • Public Cloud
  • Webinar Library
  • TiPs
  • DRAW
  • CPE

GitHub Copilot in Microsoft Teams & AMA

Github
11/16/2026
0 (0%)
Share
  • Comments
  • Download
  • Transcript
Report Like Favorite
  • Share/Embed
  • Email
Link
Embed

Transcript


笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ 笙ェ Hello. Hi, friends. Good morning, good afternoon, good evening, depending on where you are tuning in from today. It's a beautiful day, a beautiful week. Thank you all so much for joining. I'm seeing the chat and I'm loving what I'm seeing already. So please, if you have not yet introduced yourself, please let us know where you're tuning in from. I myself, I am tuning in from Nairobi. It's 1.36 p.m. right now. I am incredibly happy to be on this livestream with you all. Looking forward to connect, looking forward to having some great discussions and conversations, so feel very much welcome. I'm seeing a lot of activity already from the chat coming in from LinkedIn. So we are live on LinkedIn, Twitch, and on YouTube. So feel free to introduce yourself, let us know where you're tuning in from. I see we have a question here from Ali. Hey, Ali, welcome to the stream. I'm assuming this is your first time here. So Ali here is asking, can someone please tell me what this event is about? And I see that we have Jayesh, who's already jumped in on this question and given an amazing response to the question. So Jayesh, thank you so much. I think you'll be my co-host for today's livestream. So yes, this is Rubber Duck Thursday. It is our weekly livestream where we come together, join the community, just have conversations around everything related to GitHub. If you have any questions, we just go through your questions. Sometimes we do some live project builds together. We go through any announcements that we've had from GitHub in the last couple of days. So it's really just as Jayesh puts it here. It's an informal developer session where we get to connect and have conversations. So normally we do have themes set for every week, but for this week, I'm actually opening it up and we'll have today's conversation being driven by your questions. So if you have any questions, you have any topics, you have any demo asks that you have today, I am actually opening it up. Let's have a conversation that is cleared by what is top of mind for you guys today. So that's basically why we are here. This livestream happens every Thursday, and we do it across three different time zones. So this is the first one in the EMEA-friendly time zone. We'll have one in Spanish later on, and then we'll have one that covers the Americas time zone. So you can always hop in and connect to the community across these different livestreams. All right. Great, great. I'm seeing everyone excited to read your comments. Yes, Jayesh, you are correct. This is a weekly livestream. So every Thursday we are here ready to connect and take questions from the community. Right. Hey, Akun. Hey, Bruno. This is an awesome colleague of mine. Hi, Bruno. Good to see you on the chat. So yeah, if you have any questions, please put them on the chat. Today's conversation, as I said earlier, will be steered by what you guys want to talk about. So if you have anything you want us to discuss, this is the right platform. This is the right space for you. We have representation from across the world. Welcome from Australia. We have Adamson joining from Zambia. Welcome to the stream. I have a LinkedIn user here who's joining from the States. Welcome, welcome. We have Andy from the UK. Fantastic. So just drop your intros. If you want to connect to the community, you can always do that in the chat. All right. Welcome, Gaurav from India. Yes, it's all about GitHub. So if you have any questions or anything specific you want to talk about, let's go ahead and do that. All right. Fantastic. Marcos, welcome from Brazil. That's great. All right. Yeah, I see we have a LinkedIn user who's sharing a summary of something they're also building. So yes, if you're building some exciting project, you can also do that. So you're building Skillhawk. You can just read that on the chat. An open source AI agent security lab where students fork the repo and GitHub Actions automatically creates security challenges. That sounds really, really interesting. It's a long comment. I'm just going to pop it on the screen. But this does sound like a very interesting open source project. There's a link to the repository there. So if you want to check it out, go ahead, connect with, I'm seeing LinkedIn users, so I'm not seeing your exact username, but the project is Skillhawk. If you're interested in learning more about it, if you want to contribute, then feel free to connect with our LinkedIn user today. And thank you for sharing that on the chat. That's fantastic. All right. Good morning from Brazil. All right. Vishal, confirm if you're having trouble getting my audio. If that's what you mean by the comment that you just dropped on the chat. All right. There's a question that has come in here from Tanmay. For someone who's learning AI machine learning and software development, what kind of open source projects would you recommend contributing to in order to build a strong GitHub profile? That's such a great question. And Tanmay, before I directly answer the question, I'm just going to share some specific resources for the open source community. So allow me to just share my screen. So I'm just going to share some of the resources that we have specific that target open source contributions, maintainers. And then from there, you'll definitely find a path that will allow you to explore more open source opportunities. So let me just pull in my screen over here. Should have done this before the live stream, but no worries. There we go. Right. So I'm going to share the first resource I'm going to share for you is just as we have this live stream every single Thursday. On Fridays, we do have a separate live stream that is the open source Fridays. So this is where you can join us right here on the GitHub channel on YouTube. And then we bring on board maintainers and just active maintainers of different open source projects. They talk about their projects. They talk about opportunities to collaborate. And I believe that, Tanvi, this would be a good starting point for you. I'm just going to pop that link on the chat right there for you. And then I'm going to put it on the screen as well. So on the YouTube channel on the GitHub channel right here on YouTube, you should be able to find the open source Fridays playlist. So every single Friday, we do have one of our team members who hosts these amazing sessions. And then we bring in maintainers who talk about the projects they're maintaining. And as I said, if you're looking for collaboration opportunities, then that's definitely a good place to start. So Tanvi, that would be the best place to get started. And then directly to your question. Your question was more specific in terms of what projects, right? So what projects would you recommend contributing to in order to build a strong data profile? One, I would say, I would ask you, what is it that excites you about building software, right? Are you more into building AI projects? Are you more into building, I don't know, physical AI, for instance, automations? Then just find projects that align with the skills that you want to build. And right now, it's interesting because you can be improving on your skills. And at the same time, you're working with AI agents alongside your contribution. So it's just a matter of finding, what is it that excites you? What is a specific skill set that you want to grow? And then just align the project or the open source projects that you're looking at towards those specific skills. And again, it's also the best time to challenge yourself. So if there's a skill you've always wanted to try, but you've never had the chance to actually do that, it's incredibly easy right now working with agents to even build projects in a programming language you've never used before or just work with a stack you've never worked with before. So I would say this is the best time to just go all in. If there's any idea that you've ever had and you've had very limiting factors before, right now I feel would be the best time to experiment with. So I've just shared this open source findings playlist with you. Just have a look, go through and see some of the projects that have been hosted on this show. And then if you find anything interesting, just go ahead and start contributing. just go ahead and start contributing. All right, I'm seeing more comments, people introducing themselves on the chat. This is great. Welcome Dr. Mathias from Germany. Welcome on the show. So again, as I was saying before, today's theme is basically going to be questions from you guys. So if you have any questions, I'm going to use your questions to sort of steer the direction of the conversation today. All right, we have a LinkedIn user who's asking here, what about co-pilots in Azure in the mean of language? Right, I don't think I understand your question clearly. Probably you can just rephrase it a little bit, but I will try and answer what I think you mean. If I'm getting it wrong, please do correct me. But your question is what about co-pilots in Azure? So yes, we do have a co-pilot that sits on the Azure portal itself, right? So if you want to ask questions about your resources, you want to ask questions about the services that you have deployed in your Azure subscription, you can work with co-pilots directly on the Azure portal. But on top of that, I acknowledge that most of you here are actual developers. So probably you're spending most of your time on your IDEs, on your development environments. So instead of having to context switch, so you hop, let's say from VS Code, go on the Azure portal and back, we do have the GitHub, we have like an Azure skill that allows you to connect GitHub co-pilot directly from VS Code, and it will just connect to Azure subscription. So I think for that, I'm going to probably just pull in my VS Code and see if I can show you how that looks like. So, okay, I opened the GitHub co-pilot chat over here. It looks like you're not seeing my VS Code window. Okay, just a second. All right, let me just re-share my entire screen. All right, so hopefully you should be able to now see my VS Code. And what I want to answer is the question, okay, can I use co-pilots to manage my Azure resources, my Azure services? So let's look at how that path would look like. So I do have the Azure MCP server installed, right? So that's the first thing that you can look at. You do have the Azure MCP server, which allows you to connect to your Azure subscription, and then you can have GitHub co-pilot report on let's say the status of your deployed application, the status of your container, status of your cloud services, all that within your development environment. So this here is VS Code. You can connect to the Azure MCP server as well as the Foundry MCP server. So assuming that you're building agents and you want to let's say deploy models in your Azure subscriptions, then you can work with the Foundry MCP server, which gives you access to the different models that you have access to. And then just to add on top of that, there is an extension that is called the Foundry Toolkit extension. So if you go over to your extensions tab on VS Code, and then just look for Foundry, you have the Foundry Toolkit. Now this Foundry Toolkit is think of it as a toolkit for everything that you need to build agents. So yes, your primary agent that you're likely working with on VS Code is GitHub co-pilot, but GitHub co-pilot helps you build software with AI. But what if you want to actually build the AI? What if you want to build an agentic experience as part of your product? And that is where Foundry comes in. And once you have this Foundry Toolkit extension, then one, it allows you to access the model catalog. So you can see the different models that are hosted in Foundry. Yeah, let's see if we can scroll past. Yeah, so you can see the different models that are hosted on Foundry. You can evaluate them based on the agent that you want to build. You can deploy AI agents right here from VS Code. You can complete your evaluations. You can set up evaluations for your agents. So I highly encourage you, if you're looking for that integration between co-pilot and Azure, yes, you can use the Azure skills. You can use the Azure MCP server as well as the Foundry MCP server. So I hope that answers your question. All right, hey from Turkey. Hello from India. Wow, so many people on the stream today. Okay, we do have a question. So Dr. Mathias is asking that, hey, I'm going to give a talk about GitHub Co-pilot soon and will present the Rubber Duck feature as well. Do you have an example repository that I can showcase for Rubber Duck that way I don't have to prepare anything? Yeah, that's a great question. And yeah, from my experience with the Rubber Duck feature, in case you're hearing about the Rubber Duck feature for the first time here, just a quick summary there is with the Rubber Duck feature, and let me just show you this via the Co-pilot app. So what the Rubber Duck feature allows you to do is, we have Rubber Duck. So Rubber Duck is basically, you can think of it as a critique. So you're intentionally introducing a layer of having one agent critique the output from another agent. And how it's implemented in GitHub Co-pilot is that if your primary implementation is being handled by an agency from Anthropic, then the Rubber Duck review is going to come in and provide critique by an agent from OpenAI. So this way you're having cross-model family critiques and reviews so that if there is a limitation with one set or one model family, then the other model family can come in and just sort of fill in the gap. So that's the whole idea of Rubber Ducking. So Dr. Mathias, to your question here, I would actually suggest that you work on a project that you're very well familiar with, because the whole idea of Rubber Ducking, you want to really show how powerful this capability is, is it would be best showcased if you have like an implementation, let's say you have a project you're familiar with, you want to add a feature, you want to change to a different approach. So you can basically just show one agent, do the whole implementation, and then just ask the Rubber Duck agent to come in and perform the critique. And then you can just walk through that critique yourself. So I don't think you'll find so much value in using like a sample repository for this, but this works best if you actually just fit it as part of a project that you're familiar with, a project that interests and excites you, and then you can just use the Rubber Duck agent there to critique one of the implementations that has been done. So in terms of preparation, specifically for the Rubber Duck feature, I would just say it's a matter of having one agent implement a feature, and then have the Rubber Duck agent come in and provide a critique, and then you can just go on that critique with your audience. Yeah, so yeah, I don't think that like having an example or a sample repository would do you justice, and wishing you the very best in your talk. All right, we have a question here from Asta, who's asking, hey, can you please give some more details about the reason it helped out here? Don't understand what caused it. Yeah, so yes, this week I was off to a rough start, apologies for that. So that's a good question, and what I'll do is there's a report that was published that summarized the incident, what happened, what went wrong, and how it was resolved. So I'm just going to focus on the chat in case you want to read deeper, but specifically to your question, in terms of understanding what caused it. So basically it was, let me just try and find that for you exactly. Yeah, so some of the failing traffic here was not from Central US, and yeah, the immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. So it's basically one of the services that fails to autoscale correctly that ended up triggering that series of latency and errors that we experienced on Monday. So if you'd want to just read more about the incident itself and what the team did to resolve it, I have shared the report that was published that explains all this in depth for you. So yes, you can have a look at that, and hopefully it will give you some visibility in terms of what happened and the steps that the team will take to prevent this from happening. All right, well, that's a good question. Again, I apologize for a rough start of the week. Monday indeed was a rough one. Yeah, thank you for your patience. Let me see. Just scrolling through the questions. So I'm having questions coming in from LinkedIn, from YouTube. So I'm just scrolling through to ensure I don't miss any questions. But if you feel like I have scrolled past your question, just post it again on the chat and I will surface it. All right, so Mohammed here says that the Azure Co-Pilot makes coding faster, but I still see it struggling with complex logic and non-English documentation. That's an interesting comment. And Mohammed, when you say the Azure Co-Pilot, I will assume that you're talking about the GitHub Co-Pilot here, since you're talking in the context of using it to code. So I am assuming that you're talking and referring to GitHub Co-Pilot here. So yes, it makes coding faster, but you see it struggle with complex logic. And in non-English documentation, right? So do you mind sharing some more context, like in terms of the specific model that you were using and perhaps the language, the non-English language that you were working with here? I have not really worked with Co-Pilot on non-English projects before, so I may not have some more insights to share regarding that. But in terms of having a model struggle with complex logic, I probably would suggest trying to work with more powerful, like some of the more powerful models from either Opus 5 or GPT 5.6. So just seeing if there's a complex task, that definitely a small model or a versatile one, the versatile models would struggle with the task a little bit. So if you're trying to work with a powerful model, it's still not able to work through the complex logic. You could maybe then supplement that with your own instructions. If you have your own custom instructions, if you could give it or add in skills that will allow the agent to just know more how to unblock itself when it hits some specific blockers, then I think that should overall improve the quality of output that you get. But in terms of the complex logic, yes, I would say if you are aware that the task that you're sending co-pilot here is one that is considered complex, then I do recommend you just post directly to a powerful model. At least have it probably working in high reasoning effort, just so it can reason over the complex logic, then hopefully you get some improved quality of the output. Yeah, but yeah, if you could just drop like the model that you tried using and probably just the language that you're trying to work with. Yeah, I'll just dig in and see if there's some non-limitations, like in terms of a certain set of languages that this model will struggle with. I have not heard of any so far, to be honest, but that would be an interesting thing to look at. All right, we have a LinkedIn user who's sharing one of the projects they're building. So do have a look if you are interested in that. Right, so Michelle is asking, hey, can you tell me about cybersecurity, how to improve my GitHub profile and what projects to make? Yeah, so good question. I may not speak so much about cybersecurity on its own, but in terms of just your overall security posture right now, security posture right now, and I think the biggest challenge that almost everyone and and I think the biggest. most open source maintainers are facing here is in terms of, you know, just the tax office has actually changed right now, having coding agents, and as much as agents can be used for positive or for good, we do have bad actors who also amplify their efforts using coding agents. And so as a maintainer or let's say as an individual contributor, how do you just improve on your security posture? So towards that question, I am again going to share one of the resources that we have on the GitHub blog. So just I believe it was this week or last week, yeah, last week, we had one of the blogs addressing like the top security vulnerabilities that open source maintainers have actually reported. And this I believe is a very useful blog because it goes a step further and walks you through entirely the entire process that these large open source projects were able to take, like the actual process they were able to take to ensure that they were improving their overall security posture. So the blog here is, and I'm going to, I'm going to share this with you on the chat. And let me just put it on the screen as well. Right, so it's what 50 open source projects taught us about security in the AI era. I do highly recommend that you take a read, just go through the blog. And one of the key things that stood out for me is that this is actually part of a series. There's a program here called the GitHub Secure Open Source Fund Program. So the idea here is that the GitHub Security Lab actually works with some select open source projects and they take them through the entire process. I'm just trying to just scroll through where we have a description of what the program is and how it works. Yeah, so basically projects that are part of the Secure Open Source Fund, what happens is that as soon as you join the program, then you do get some bit of funding and you get to work with the GitHub Security Lab experts and you're working alongside the trusted community here, of course, and then you go through a three week sprint of just sessions that involve training with the security experts. And then you get to work on an actual plan that will help you identify security vulnerabilities in your open source projects and then work with you and discover how you can actually fix and address some of these issues. So one of the projects that, of course, went to the program was OpenClub and through this blog, they've actually shared like a summary of what OpenClub project went through, the entire session, the entire series of events and training that they went through and then what the outcomes were. So after going to the program, the outcomes where we have like OpenClub identify real security vulnerabilities and work through like a remediation framework for that open source project. So I believe that this would probably shed some bit of additional light and just give you insights on what are the new attack practices or what are the new attack mediums that bad actors are using and then how you can protect yourself from such attacks. So this is really a good blog that you can have a look at and hopefully get some better understanding of how that looks like. Yes, I see many questions coming in. Right, I'm seeing a few more comments related to the incident, the outage that happened on Monday. So, yes, the incident report that I shared should hopefully address some of these questions that I am seeing. All right, let's see the next question. So what are the most important GitHub skills that a beginner should learn first? OK, yeah, good question. I would again. Yeah, so I think I'll also just point you to some of the resources that we have existing. So one on the GitHub YouTube channel, we do have a playlist here that is specific for beginners. So if you want to learn, let's say the GitHub Copilot app, this is a new agent native application that just brings together all your work in one platform and then you can have agents just working parallel across your tasks. Then we have like a dedicated playlist for an introductory, an introductory level explainer of the Copilot app. We do have the GitHub Copilot CLI for beginners. So if you want to understand how can you work with Copilot from the CLI in Metaminal, then that's a playlist that you can have a look at. And then we do have like GitHub for beginners. So I believe this is what Nandani is asking here. So as a beginner, what should I look at? I think most importantly, in as much as we're talking so much about Copilot, just understanding the very basics of what Git is, what GitHub is and how you can use it, how you can manage projects, how you can collaborate with different teams. Then I do believe that the GitHub for beginners playlist here in Nandani would be the best place for you to get started. Get the fundamentals of Git and GitHub as a platform. And then from there, just work through the additional skills to see how you can make your development journey a bit more better with the use of AI agents. So I would recommend that you have a look at the GitHub for beginners playlist. That way, get the fundamentals of the platform. And then from there, work through the additional skills that help you be more productive. All right. Just scrolling through the questions. All right, so Tadme is asking, with AI increasingly becoming part of software development, how can developers use AI coding tools effectively while still developing strong fundamentals and genuine problem solving skills? That's a great question. That's something that I've actually had to struggle with myself for some time. And I'll open it up for anyone who wants to respond to this question on the chat. Please feel free to do so. But what I'll share myself is that, yes, I am a firm believer that in as much as AI is really getting to a level where it can do almost everything to an acceptable quality path. So that's the reality. That's there to stay. We're only seeing these models get better. I am still a firm believer that we will need developers who know what they're doing. Even now, in the near future, we'll still have that need where you can actually have someone look at a problem or look at an AI implementation and say that AI had it wrong. Someone who has built the skill mastery to call out when AI does something the wrong way. So that's the first thing I will share that, yes, there is still a need for you to master fundamentals, get your actual experience in, get your actual time in building and designing architectures yourself. So that's probably like the basic that forms the basis of the response I'm going to share next. And then the question here is asking how can developers use AI coding agents or tools effectively while still developing strong fundamentals? So, yes, I would share on the tips that I'm trying to actually implement, which is having very clear boundaries in terms of what you want the agent to do and what you need to do yourself. So what I mean by this is, now assume I'm starting a new project. At the very beginning, there are decisions that need to be made. And what I do is I ensure that I am the one making those decisions. So what approach do we take? How do I design the architecture? How do I design that whole flow for my project? I ensure that I take my time to sit with that plan. So if it's the agent coming up with a plan, I have to go through that plan line by line to ensure that, yes, it's either I am just okaying the plan as it is, or I'm just coming in to ensure that it's an architecture that I am actually comfortable implementing. So at the very beginning, before I send off agents to work on different parts of the project, I want to ensure that the agent will actually enforce what I have in my mind. So that's a way that I try to ensure that I'm challenging my mind enough. So I'm exercising my brain muscles to ensure that I'm thinking about problems. Again, the other mismatch that I would actually call out is AI agents will probably just implement what you ask them to do. But in terms of mapping a solution to a problem, that's still an area where you, the human in the loop, probably have the better understanding. You understand the problem best. If it's a project that is designed to solve a societal problem, you're the one in that society, you're the one who really understands the depth of the problem. And so it's up to you to kind of have that problem solution mapping in your head first before you're able to relay that to the agents. And yes, software development is not all about writing code. There's the aspect of problem solving, which is what you get to exercise when you don't delegate. You're not delegating the part of thinking about the solution to the agent. You think about the solution and then you send off the agents to implement that solution on your behalf. And throughout that process, you feel like, yes, as much as I'm sending my agents to build a certain aspect of my project, that is a skill that I want to perfect myself. It is totally okay to switch off the agent. It's totally okay for you to not delegate to the agent. Do you feel like I want to improve on, let's say just my JavaScript skills, right? Just open an ID and switch off all the AI. You are allowed to do that. Get your skill mastery in. Once you have the basics, once you can do something on your own, then it's better to now at that point, delegate to the agents. This way, if an agent goes off in the wrong direction, you're able to call it out and steer it in the right direction. So I hope that helps a little bit. And again, if you have some responses to this question, feel free to put them in the chat there. But Tanmay, thank you so much for the questions that you've been asking. Okay. Right. So many questions coming in. Again, if I scroll past your question accidentally, just feel free to drop it a second time on the chat. All right. Jayesh is reporting some bit of lagging. So just confirm for me on the chat if you're also getting some lags. All right. So Anand is asking, can GitHub Copilot analyze logs of GitHub actions and comment the results on the PR? So I would say yes. I would say yes, because GitHub Copilot also sits on GitHub.com, so you can have it look at your repositories right there on GitHub.com. You can have it look at your actions. If an action fails, then yes, you can also have Copilot explain, let's say, certain jobs are failing. You can actually point Copilot to the specific failing jobs, have it investigate, and then have it basically open a PR that addresses the issues that are failing in your job. So the answer to this question is yes, you can have Copilot basically look at your work flows, investigate, and fix or propose a fix in formal PR. So that's most definitely possible. Yeah, so Matthew's here. I believe this is a response to the question that was asked earlier about, hey, what skills do I learn right now that AI can do almost everything? And I think this is a very good take. Don't necessarily learn the specifics of the problem language, but instead learn the logic, learn how to solve problems, learn how to translate a problem into code. I think that's a very good answer. I think that yes, the emphasis now here is on the problem solving aspect, the logic itself. How do you translate a problem into logic that results in a solution and not necessarily spending so much time on getting a handle on the syntax. Let's say the syntax of a programming language. I think that's a very, like learning the syntax of a language is sort of trying to cram a And that's exactly what AI is very good at. So it wouldn't make sense for you to spend so much of your time cramming the pattern that is cramming a programming language syntax, but instead focusing on the logic. So Matthew, I do agree with your comments there. okay um we have another question here so for a developer who already builds with github but wants to move towards professional software engineering what github skills or workflows would you recommend mastering next so you already know how to build with github what should you master next especially around git code reviews cicd and collaboration that's that's a fantastic question and um yeah I'm also going to give it an attempt and of course if you are on the chat you feel like you want to contribute to answering this question please go ahead and do so so what do I recommend you master next so one I would say trying to understand how agents fit in your overall workflow so yes you do have your workflow assumes the traditional stlc you're moving from planning there's designing implementation you do have your deployment you do have your testing so try and figure out where can ai agents actually come in and give you the most or the best result or the most optimal outcome what roles can you delegate to ai agents what would you rather still remain in charge of right so I would think about I want to now understand the full software development life cycle when it comes to testing what can I delegate to the agents and what do I need to be there how that human will look to okay and and probably just um ensure that you have a set of human eyes looking through requests looking looking through um um code reviews right so I think that would be the next thing I would recommend you already know how to build with github so it's just a matter of identifying as part of that full workflow where will you get the most benefits by delegating agents I think that collaboration piece that you mentioned at the very end would be collaboration with both human developers as well as coding agents because coding agents are here to stay so learning how you can effectively work with agents know how you can handle either between yourself and the agent between one agent to another agent so just managing that collaboration aspect across human teams and human agent teams I think that would be the next piece to focus on because for most like job interviews or job descriptions that I've been seeing so many organizations are actually very keen to understand if you're bringing on someone who is going to be building software with us do they understand how to interact with coding agents because at the end of the day yes they called that the agent will deliver the code but you need to be accountable you need to need to be there to answer about the output that gets generated from the agents how can you give these agents the right amount of context right how do you give them access to the right platforms have them pull in the right context to give you the best outcome so I think that's the next phase of hey I know how to build software but now I want to understand how do I successfully collaborate with agents how do I set boundaries with my agents boundaries that these agents will appear to this you're not having any incidences that hey an agent went off did something in the production environment you do have full control over the human agent workflow so I think just getting familiar with how are these models improving what are the strengths or that what are the limitations and how can you come in to fill in the gaps okay so that's the one take that I'll share but again anyone on the chat please do feel free to jump in on the question so Robin is asking if there's a recording of this so the this session will still be on demand on the same link so you can always come back in and re-watch it or if you can always come back in and just go through the recording all right yes so learn the logic and how to solve the problem fantastic okay great yeah those are really good questions and yeah just keep them coming keep them coming I'm going to probably do one let's look at something from the changelog probably we can just go through the changelog and then just summarize what's new since the last live stream we had last week Thursday so I'm going to refresh the changelog because it happens that new releases and improvements actually published when we're live on this stream so let's just go through what's new yeah so we have good ql the latest version here improves github actions queries and javascript modeling yeah so that's on a security angle let me just drop this link on the chat again so it's github.blog slash changelog if you want to see what's new what has been um what has been published on github within the last couple of days that's that's the site that you can have a look at so there's an improvement here so now organizations can track organization code quality trends that's interesting so this means that the organization level code quality dashboard now includes a trends tab so at the top here you will see next to the health tab you will see a trends tab so this trends tab shows you how the code quality has changed across your repositories over time so I think for organizational organization admins if you just want to get a feel a better understanding of hey how have our repositories been performing from a quality standpoint over a given period could be 7 days 14 days 30 days then with this new improvement you will be able to see that under the trends tab so you'll go under the trends tab and you'll be able to see just that progression on the quality across the different repositories in your organization so I think that's a really good improvement so for the admins of the live that's one change slot that is worth reading is to understand exactly what you need to enable it is it on my default and how you can basically just have a better understanding of the code quality trends across your repositories so that's that's that I think it's a good one that was launched just yesterday so do have a look and let us know what you think then enterprise managed settings are now available in copilot for jetbrains so if you're using the jetbrains IDE suite then you should be able to have access to the enterprise managed settings for github copilot that's something that you can look at have some more improvements on a security angle then yeah this is one that's that is interesting so as of last week this is actually this was actually published last week so as of last week now all apps support multiple redirect URIs and token refresh so what does that mean that means that right now assuming you're working on different projects and you want to set up or have like different environments you're not now limited to just adding one redirect URI application you can set up your auth application and then add up to 10 redirect URIs on the same application now before if you wanted to like configure five different your redirect URIs you'd have had to create five different four applications and add one URI for each application so as of last week now we have support for multiple redirect URIs so if let's say you go on your you go on your settings page let's just look at how that would look like go under the developer settings for your auth applications if you create a new auth application then you should be able to see add a redirect URI button and this allows you to add multiple your redirect URIs you can add up to 10 for the same application and then something I also call out here is that wildcard matching will allow the tokens to be sent to all sub-planes right so assume let me just go back to the yeah yeah so we have like the option for you to enable wildcard matching so that means that you can have the redirect either hit related sub-domains for application so that's something that you can also enable right there when you're creating a new auth application so this here has been a big ask from the community and just to give you some additional context in terms of how we got this to be launched last week is this actually stemmed from a simple tweet right or yeah you can't call them x but a tweet on on x where after we shipped stack PRS a couple of weeks back we had just someone from the community share some of the features that they want to see next and this was just last month yes this was in July and then just after sharing that hey I want to see multiple redirect URIs for all applications just a month later we see that already implemented so just sharing this to give you the assurance that your feedback matters if you have any feature requests you have any suggestions please reach out to the team on x very responsive the product teams are very open to learning about what features do you want to see supported next and just as you've seen the turnaround here was like a month and you can basically just have github github be the platform that you want it to be so if you have any feature requests please do tag us on social media and of course we'll be more than happy to follow up and ensure you get the features that you are hoping hoping to to see okay um right so my nick i see your comment there that you're you're unable to access your github account uh please do you mind just sending me a direct message probably on on linkedin i'm happy to just work work with you and see if we can escalate that apologies for that so just send me like a direct message see if there's something that we can do about it yeah uh pause for a minute see if you have any new questions coming in all right any new questions cool so the last thing that i will share is um we have something that actually dropped yesterday but i think it was a soft launch we're yet to see some social comms go out but we'll likely see some communication code today in the course of today but we have a new integration for github copilots within microsoft teams and i'll just give some context here because i want us to start from what problem is being solved before we even talk about what feature does so i just wanted to think about you know like within your organizations right within organizations where do most impactful discussions happen you know like these um insights this unfiltered opinions from your colleagues where do these conversations happen i bet they all sort of happen in the um collaboration platforms that you have in this case it could be teams like just um group chats or just threads on teams this is where you have very key discussions going on very major decisions being made and feel that unfiltered opinions we have so many people sharing honest feedback within platforms like microsoft teams but then the code the code that actually needs to be implemented or needs to be touched in order to resolve some of this feedback sits or lives in github so that right there means that after a discussion takes place on let's say a team's thread or a team's channel someone would have to go back to that discussion summarize everything and then go over to github log an issue do that manual handoff just transferring the context if let's say someone shared on teams that hey a certain feature is not working and then the engineering team has a conversation back and forth conversation someone will have to come in and then just do that manual transfer in hand of your github issue and then probably have copilot take up that issue so that's the manual step that this integration is actually looking to fix so with this integration that means that you can now have github copilot as part of your team's discussion so yes your team will have a discussion and then as soon as you have an action item that needs to be taken you can now add mention github right there in teams then github is going to use that entire thread to get the right context so that means no one has to go in capture the context and transfer that on github github will through copilot it will capture the relevant context and then go in and just submit a proof request now i want to show you this in action So I'm going to We're going to have a look at how this looks like So I hope you can all see this So there's a demo here that I just want us to talk about And hopefully this will give us a feel of you know, how would it look like working with GitHub copilot? Within the channels that you're already working on So the scenario here is that we have our thread right and then Priya here Raises an issue that hey, is anyone else seeing this? Let's leave the bill invite won't open for me on iPhone and She attaches a screenshot so you can see clearly the feature here is broken So as part of the thread we have Diego who comes in and says that hey I have tried the same feature on Android and it works It loads just fine and some here confirms that it's the same experience on the web and then just share some bit of Additional details in terms of what they are seeing for the errors so I've confirmed in the logs that the invite screen calls a certain endpoint and it's 500 in every single time and since Android hits a different path it never notices though So that's why the bug is only in the iPhone implementation, but it works well on Android now the developer who's Basically supposed to work on this feature is stuck on a payments migration Right, and they're not entirely sure in terms of what could be wrong So what happens is that they tag GitHub right here on things and then they don't have to repeat the entire issue To GitHub because now GitHub is part of the conversation So it's up here at the target GitHub and ask it to reproduce the error and then find the root cause So this is like an investigative task for co-pilots Co-pilot instantly being part of the conversation and having visibility over the entire thread is able to reproduce the Issue and then at the end of it all it opens an issue on the repository Right again at this point No one is leaving teams to go over on GitHub to do that manual transfer of context Everything sits within the same channel and then Jordan here decides to just tag GitHub and ask GitHub to go ahead Fix that issue and open a pull request and then after opening the pull request GitHub co-pilot here should share a screen of the working feature and GitHub the coding agent here or the cloud agent here Implements that And then GitHub is able to share a screenshot of the working implementation So this is how that integration would look like You can see that the team here acknowledges that hey, that's exactly what is expected From the app and co-pilot was able to gather the right context Go off, implement the feature and then come back with a working solution, a pull request that is ready for review So, yeah, that's the Integration feature that was I believe it went live yesterday and in terms of how this happens Of course We do have some security in place because the first thing you would realize is that as part of that thread Right as part of that thread not everyone might have access to the repo that the coding or the cloud agent here is Modifying so that means by default within that thread only users who have right access To the target repository can invoke co-pilot as part of that conversation So that means if you're all in that thread and I probably don't have right access to the repo that is connected Then that means I cannot ask GitHub co-pilot here to start working on the same issue So that's like just a security feature that is in place to ensure that co-pilot here works within the permission boundaries that have been established and Then the other bit is that co-pilot here can only touch the repository that it's connected to So it won't have visibility on any other repo You basically just scope a channel or a thread to one Repository and that's the only report that co-pilot will work on if it's triggered from that thread So I think that's a really good It's a really useful feature. So think of like a work environment where you have so many conversations position points all sitting within Meetings on teams or just threads and chats on teams instead of manually transferring the context And then log manually log your GitHub issues and then assign coding agents to that you can now bring in the cloud agent Directly on Microsoft Teams so you can add it to a channel you can add it to a thread you can send a direct message right and then this way the agent will go off work in a secure sandbox and just Give you a pull request that you can review. So I think that's a pretty pretty useful feature I will share the link to the documentation again We'll probably see some more communication about this go out in the course of the week But this is something that if you feel could be useful. It's worth looking at a few things to note here is that yes in terms of Having co-pilot adhere to the set permissions or the boundaries that have been Searched the agent here will work in a secure sandbox and then is that the identity that co-pilot uses will depend on whether you interact with it in a direct message for the young or If you're interacting with it on a shared context But just as you've seen if you're invoking co-pilot as part of a thread then that influences the identity That co-pilot is going to to to adopt, right? So that means if you use co-pilot here in a direct message That means the agent here can take actions on your behalf so if I send a direct message to co-pilots and teams and ask it to Implement a certain feature and open a PR that will be the agent acting on my behalf So the identity that will show up on GitHub will be my identity, right? And it's going to use the permissions that I really have but then if I'm using it in a shared context That is either a group thread or a channel Co-pilot creates artifacts such as the pull request and it's app identity rather than a user's or single user's account, so that's just something that is very Important just to have on the back of your mind Which influences the identity that co-pilot uses when you're using it in a context of both teams in this case Then yeah, what we said earlier is that only the users with the right access to a repo can trigger co-pilots to make the changes But more importantly anyone who's part of that conversation Their input matters So if you have a thread with external partners external collaborators, yes, they don't have right access to the repo But since they've provided their input their suggestions their feedback through that chat Co-pilot is able to Take into account their contributions and their feedback And then whoever has access to right access to the repository can trigger co-pilot, but all the context Goes into informing how co-pilot addresses the task So I think that's a really really good feature. If you have a chance just go ahead and try it Um, yeah, this this documentation page has everything you need in terms of how you can install the github app on teams um as soon as you install it, then you'll be prompted to Connect to a repository and then you can have um co-pilot take actions on that connected repository Okay, so that's that's an interesting one. I wanted to share that with you So if this is relevant, go ahead try it if you have feedback, please do let us know what you think If something doesn't work again, let us know what you think happy to channel that feedback to the engineering team And yeah, I think I see we're out of time. So let me just see if we have any last questions before we leave All right abdul looks like he wanted to say something there for beginners go ahead and just drop your your comments on the chat Fantastic, right, I think this is a good this is a good place to stop Um, remember we do have another instance of this live stream. So you have one in spanish and one um later on in the in the days or just just look at the channel the github Channel right here and then you can just join any live stream that you want to be part of and I'll just put it in the comment And if you have any questions or comments, please just drop them in All right. Thank you so much for joining again Let's connect on social media if you want to chat if you have any feedback suggestions, please drop them and Be happy to work with you Okay, have a good rest of your day your Evenings, uh, take care. I will see you all next week. Hopefully You You You

TL;DR

  • Rubber Duck Thursday is GitHub's weekly global AMA livestream, open to community questions across LinkedIn, Twitch, and YouTube in three time zones each week.
  • A Monday service outage was caused by network saturation on Central US load balancers due to a traffic spike and a service that failed to autoscale; a full incident report was published.
  • For complex Copilot tasks, the host recommends routing to more powerful models like Opus or GPT-5 with high reasoning effort enabled, and using custom instructions to help agents self-unblock.
  • A new GitHub Copilot integration with Microsoft Teams allows developers to @mention Copilot in any thread, letting it read full conversation context, open GitHub issues, implement fixes, and return pull requests without leaving Teams.
  • Security controls in the Teams integration enforce repository write-access permissions per user, scope each channel to a single repo, and distinguish identity between direct-message and shared-thread invocations.
  • GitHub's responsiveness to community feedback is highlighted: a feature request posted on X in July was shipped within a month, reinforcing that tagging GitHub on social media is an effective feedback channel.

Community AMA Format and Weekly Cadence

This episode of Rubber Duck Thursday is GitHub's weekly community livestream, broadcast simultaneously on LinkedIn, Twitch, and YouTube across three time zones — EMEA, Spanish-language, and Americas — making it accessible to a global developer audience. Rather than following a preset theme, this session is opened up as a fully community-driven AMA, with the host fielding questions live from participants joining from Nairobi, Zambia, Australia, India, the UK, and the United States. The format is intentionally informal: a space for developers to ask anything related to GitHub, discuss recent announcements, request demos, and connect with peers. The host also addresses a service incident from the prior Monday, explaining that network saturation on load balancers in Central US — caused by a traffic spike and a service that failed to autoscale correctly — triggered the latency and errors experienced that week, and directs viewers to a published incident report for full details.

GitHub Copilot and Complex Logic Guidance

A community member raises a common friction point: GitHub Copilot accelerates coding but struggles with complex logic and non-English documentation. The host acknowledges this limitation and offers practical guidance — for complex tasks, developers should route directly to more powerful models such as Opus or GPT-5, and consider enabling high reasoning effort mode so the model can reason through multi-step logic rather than defaulting to pattern-matching shortcuts. For non-English language contexts, the host notes limited personal experience but encourages the viewer to share specifics so the team can investigate whether particular language combinations surface model limitations. Custom instructions and agent skills are also suggested as a way to help unblock agents when they hit recurring obstacles in complex codebases.

Open Source Security Posture in the AI Era

In response to a question about cybersecurity and improving a GitHub profile, the host highlights a recently published GitHub blog post — "What 50 Open Source Projects Taught Us About Security in the AI Era" — as a highly recommended resource. The post is part of a series and walks through the top security vulnerabilities reported by open source maintainers, along with the concrete steps large projects took to improve their security posture. The host notes that the threat landscape has shifted materially: bad actors are now amplifying their efforts using the same coding agents that developers use for productivity, making security hygiene more critical than ever for maintainers and individual contributors alike.

GitHub Copilot Integration with Microsoft Teams

The most significant announcement covered in this session is a newly launched integration between GitHub Copilot and Microsoft Teams. The host frames the problem clearly: high-value engineering discussions — bug reports, feature feedback, unfiltered opinions — happen inside Teams threads and channels, while the code that needs to change lives in GitHub. The manual handoff between these two environments creates friction and context loss. The new integration eliminates that gap by allowing users to @mention GitHub Copilot directly within a Teams thread. Copilot reads the full thread for context, opens a GitHub issue, implements a fix, and returns a pull request — all without anyone leaving Teams. A demo scenario illustrates this: a bug reported on iPhone, confirmed in logs as a 500 error on a specific endpoint, is investigated and resolved by Copilot entirely within the Teams channel. Security boundaries are enforced: only users with write access to the connected repository can invoke Copilot, and each channel or thread is scoped to a single repository. Identity handling differs between direct messages (Copilot acts as the individual user) and shared threads (Copilot uses its own app identity). External collaborators without repo access can still contribute context through the thread, and that input informs how Copilot addresses the task.

Chapters

0:00 - Intro Music and Stream Opening
5:37 - Welcome and Format Overview
22:17 - Rubber Duck Agent Demo Advice
23:40 - Monday Outage Explained
25:51 - Copilot Complex Logic and Model Selection
29:03 - Open Source Security in the AI Era
53:35 - Community Feedback Drives Features
55:38 - Copilot Integration with Microsoft Teams
58:30 - Teams Integration Demo Walkthrough
62:05 - Security and Identity Controls
67:12 - Closing and Next Livestream

Key Quotes

6:43 "This is Rubber Duck Thursday. It is our weekly livestream where we come together, join the community, just have conversations around everything related to GitHub."
24:25 "The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic."
27:03 "I probably would suggest trying to work with more powerful, like some of the more powerful models from either Opus 5 or GPT 5.6."
54:10 "Just sharing this to give you the assurance that your feedback matters — if you have any feature requests you have any suggestions please reach out to the team on X, very responsive."
57:05 "The code that actually needs to be implemented or needs to be touched in order to resolve some of this feedback sits or lives in GitHub — so that right there means that after a discussion takes place on a Teams thread or channel someone would have to go back to that discussion, summarize everything, and then go over to GitHub, log an issue, do that manual handoff."
62:13 "By default within that thread only users who have right access to the target repository can invoke co-pilot as part of that conversation."
65:01 "If I send a direct message to co-pilot in Teams and ask it to implement a certain feature and open a PR, that will be the agent acting on my behalf — so the identity that will show up on GitHub will be my identity."

FAQ

What caused the GitHub service outage earlier in the week?

The outage on Monday was caused by network saturation on load balancers in Central US, triggered by a new peak in traffic. A service failed to autoscale correctly, which set off a cascade of latency and errors. GitHub published a full incident report detailing what happened and the steps being taken to prevent recurrence.

How does the GitHub Copilot integration with Microsoft Teams work?

Once the GitHub app is installed in Teams and connected to a repository, users can @mention GitHub Copilot in any channel or thread. Copilot reads the full thread for context, opens a GitHub issue, implements a fix in a secure sandbox, and returns a pull request — all without anyone leaving Teams. Only users with write access to the connected repository can invoke Copilot, and each channel is scoped to a single repository.

What should I do if GitHub Copilot struggles with complex logic in my codebase?

The host recommends routing complex tasks directly to more powerful models such as Opus or GPT-5, and enabling high reasoning effort mode so the model can reason through multi-step logic. Adding custom instructions or agent skills that help the agent unblock itself on recurring obstacles can also improve output quality significantly.


Categories:
  • » Cybersecurity » Application Security
  • » Data Protection
Channels:
News:
Events:
Tags:
  • AI & Machine Learning
  • Security Operations
  • DevSecOps
  • Demo
  • Getting Started
  • Best Practices
  • GitHub Copilot
  • Microsoft Teams Integration
  • AI Coding Agents
  • Open Source Security
  • Incident Response
  • Developer Community
  • Model Selection for Complex Tasks
Show more Show less

Browse videos

  • Related
  • Featured
  • By date
  • Most viewed
  • Top rated
  •  

              Video's comments: GitHub Copilot in Microsoft Teams & AMA

              How secure is your Microsoft enterprise? Under 5 minutes, earn $10 in TruthPoints.

              View CPE Certificates

              Upcoming 360 View Events

              • Nov
                19

                Securing the Microsoft Enterprise: Strengthening Configuration Management, Identity Security, and Data Protection

                11/19/202601:00 PM ET
                More events

                XStreaminars (watch here)

                • Dec
                  09

                  Beyond Continuous Compliance: Getting Ready to Detect, Recalculate, and Adapt

                  12/09/202601:00 PM ET
                  More events

                  Industry Events (Sponsor Hosted)

                  • Nov
                    18

                    Hands-On Workshop: Connecting On-Prem Data to Databricks via MinIO AIStor (International)

                    11/18/202608:00 AM ET
                    • Nov
                      19

                      Zendesk Deep Dive: Get the work done faster with Employee Service AI Agents

                      11/19/202601:00 PM ET
                      • Nov
                        19

                        AI Agent Showdown: Discover What Muse, Dots, and Duet Bring to Your Website

                        11/19/202601:00 PM ET
                        • Dec
                          02

                          Skylight en acción: salvaguardando la IA más allá del usuario.

                          12/02/202604:00 AM ET
                          • Dec
                            03

                            CISO Insights: Steering Cybersecurity Strategies in an AI-Driven Era

                            12/03/202601:00 PM ET
                            More events

                            Upcoming Webinar Calendar

                            • 11/18/2026
                              08:00 AM
                              11/18/2026
                              Hands-On Workshop: Connecting On-Prem Data to Databricks via MinIO AIStor (International)
                              https://www.truthinit.com/index.php/channel/2194/hands-on-workshop-connecting-on-prem-data-to-databricks-via-minio-aistor-international/
                            • 11/19/2026
                              01:00 PM
                              11/19/2026
                              Securing the Microsoft Enterprise: Strengthening Configuration Management, Identity Security, and Data Protection
                              https://www.truthinit.com/index.php/channel/2076/securing-the-microsoft-enterprise-strengthening-configuration-management-identity-security-and-data-protection/
                            • 11/19/2026
                              01:00 PM
                              11/19/2026
                              Zendesk Deep Dive: Get the work done faster with Employee Service AI Agents
                              https://www.truthinit.com/index.php/channel/2181/zendesk-deep-dive-get-the-work-done-faster-with-employee-service-ai-agents/
                            • 11/19/2026
                              01:00 PM
                              11/19/2026
                              AI Agent Showdown: Discover What Muse, Dots, and Duet Bring to Your Website
                              https://www.truthinit.com/index.php/channel/2228/ai-agent-showdown-discover-what-muse-dots-and-duet-bring-to-your-website/
                            • 12/02/2026
                              04:00 AM
                              12/02/2026
                              Skylight en acción: salvaguardando la IA más allá del usuario.
                              https://www.truthinit.com/index.php/channel/2147/skylight-en-acción-salvaguardando-la-ia-más-allá-del-usuario/
                            • 12/03/2026
                              01:00 PM
                              12/03/2026
                              CISO Insights: Steering Cybersecurity Strategies in an AI-Driven Era
                              https://www.truthinit.com/index.php/channel/2231/ciso-insights-steering-cybersecurity-strategies-in-an-ai-driven-era/
                            • 12/09/2026
                              01:00 PM
                              12/09/2026
                              Beyond Continuous Compliance: Getting Ready to Detect, Recalculate, and Adapt
                              https://www.truthinit.com/index.php/channel/2250/beyond-continuous-compliance-getting-ready-to-detect-recalculate-and-adapt/
                            • 12/09/2026
                              02:00 PM
                              12/09/2026
                              Strategies for Safeguarding Endpoints in the Agentic Era with Cyera
                              https://www.truthinit.com/index.php/channel/2256/strategies-for-safeguarding-endpoints-in-the-agentic-era-with-cyera/
                            • 01/19/2027
                              04:00 AM
                              01/19/2027
                              Skylight in Aktion: Gewährleisten Sie KI-Schutz über den Benutzer hinaus
                              https://www.truthinit.com/index.php/channel/2176/skylight-in-aktion-gewährleisten-sie-ki-schutz-über-den-benutzer-hinaus/
                            • 01/19/2027
                              02:00 PM
                              01/19/2027
                              HUMAN Dialogue: Embracing the Rise of the Empowered AI Consumer.
                              https://www.truthinit.com/index.php/channel/2160/human-dialogue-embracing-the-rise-of-the-empowered-ai-consumer/
                            • 03/18/2027
                              01:00 PM
                              03/18/2027
                              Securing Access for People, Partners and AI Agents
                              https://www.truthinit.com/index.php/channel/2251/securing-access-for-people-partners-and-ai-agents/
                            • 06/17/2027
                              01:00 PM
                              06/17/2027
                              Stop the Leak: Data Loss Prevention for the AI Era
                              https://www.truthinit.com/index.php/channel/955/360view-stop-the-leak-data-loss-prevention-for-the-ai-era/
                            • 08/19/2027
                              01:00 PM
                              08/19/2027
                              Who Has Access to What...and Should They?
                              https://www.truthinit.com/index.php/channel/2252/who-has-access-to-what-and-should-they/
                            • 10/21/2027
                              01:00 PM
                              10/21/2027
                              After VMware: Building the Private Cloud You Actually Want
                              https://www.truthinit.com/index.php/channel/2253/after-vmware-building-the-private-cloud-you-actually-want/
                            • 11/18/2027
                              01:00 PM
                              11/18/2027
                              Assume Breach, Prove Recovery
                              https://www.truthinit.com/index.php/channel/2254/assume-breach-prove-recovery/
                            • 12/16/2027
                              01:00 PM
                              12/16/2027
                              The Self-Running Service Desk
                              https://www.truthinit.com/index.php/channel/2255/the-self-running-service-desk/
                            Truth in IT
                            • Sponsor
                            • About Us
                            • Terms of Service
                            • Privacy Policy
                            • Contact Us
                            • Preference Management
                            Desktop version
                            Standard version