 One more second. Okay. Backup recording is on. Tim and Shar, it's all yours. All right. Thanks, Sean. Go ahead and share my screen one second. Welcome, everyone, to the Identity Implementers Special Interest Group for March 7th. Today we are joined by Andrew Smith to give us a presentation on Jumpstart and Cloud Agent Identity. Thank you, Andrew, for joining us today. Before we pass it over to you, we have a few updates on some working groups and some announcements. So as far as announcements go, Sean, did you want to take these or I'm unsure? Yeah, I can jump on the two of those. April 2024, IIW Internet Identity Workshop is happening in Mountain View, California at the Computer History Museum. This is a two times a year event where the different clans of the identity community get together. Some folks are talking about decentralized identities. Some folks are big on open ID and there's going to be a lot of discussions around wallets. So I'm wondering if we in the Identity SIG would like to spark a conversation maybe in the next ID SIG call, talking about what folks want to talk about and present and who's coming. And maybe that could be like a five or 10 minute thing. Secondly, Open Wallet Foundation next Thursday has its first anniversary. I'll post in the ID SIG Discord channel link if you'd like to attend the registration. Basically, the presentation is going to be talking about the accomplishments for the last year and where the Open Wallet Foundation is going in the next year. Zero Knowledge Proofs and ZK Programming and Blockchain Application Development. This is a workshop that the Hyperledger is putting on. It's happening in April. The Zero Knowledge Proofs are part of decentralized identity and so that felt like a good fit. And then, thank you to Char, I believe, for putting up the recording for the Identity Plus Interop workshop that DSR put on. It was a great event and you all should definitely check it out. Also at the bottom of the working group reports and release plans, there's a note. The EU, EUDI, Reference Architecture has been, Reference Implementation has been released on GitHub. There's a link right there if you want to check it out. Open Wallet Foundation is going to do a workshop on it in a week or two. But it's not approved yet. So once it is, I'll post a link to the registration in the IDSIG Discord. That's it for me. Thanks. Awesome. Thanks, Sean. We'll jump into some quick working group updates here. It looks like the Hyperledger Indie contributors working group met on the 27th just recently in February. Was anyone able to attend this session that would like to give us a quick summary? Yep. Yep. We met last week. We had a presentation on a plugin to support self-controlable and devolvable group dids. So this is about having a did to represent a self-evolving group of dids where members can join and leave at any time. So that was really cool. Got some updates on the Indie Bezu project as well. And there was a release completed for sovereign node 1.2.0. Yeah, it's a good meeting. All right. Sounds good. Thank you, Shar. It looks like Hyperledger Aries working group met just yesterday to discuss some credential protocol reversions. Was anyone able to make this session that would like to give us a quick update? All right. Well, if you'd like to check out what exactly they were talking about, you can follow the links in this document and are on this web page rather. Aries Cloud Agent Python met a couple of days ago on the 5th. Was anyone able to attend the Aries Cloud Agent Python user group call? Yes. Yes. We met this week. We had a demo about a non-creds in W3C verifiable credential data format, data model format work. Let's see. Let's see. We also talked about updates on the non-creds RS in Akapai work. That's going well. Indorsure support just got merged in. The status of Akapai 0.12.0 release candidate 1. I believe there will be a release candidate 2 coming soon. And updates on did peer and AFJ interop and then moving closer to Akapai 1.0. Awesome. Thank you, Shar. It looks like the maintainers group met on the 27th of February. Was anyone able to attend this meeting? Yep. Pretty much what you have there just going over PRs and figuring out what needs to be done to merge them in and discussing release 1.0. So, yeah. All right. Awesome. The hyperledger non-creds met just recently here on the 4th. Was anyone able to attend this session? All right. Well, yeah, we have a quick summary here. If you'd like to learn a bit more, please feel free to go to these links here. I believe we've met since that meeting. These have all been gone through. For the TOIP Ecosystem Foundry, it looks like they've met since our last meeting together. On the 29th, was anyone able to attend this TOIP Ecosystem Foundry meeting? All right. Looks like they saw a presentation from Moby on Web 3 Battery and Burst Certificate Credentialing. So, if that sounds interesting, go ahead and check them out. The Concepts and Terminology meeting looks like they've had a meeting since our last session. Was anyone able to attend this TOIP meeting? All right. Looks like once again, some updates right here to their engine. If you want to learn more, always the link. These have not met as far as I can tell. All right. Well, if anyone has been to one of the Diff, either Didcom or Interoperability Group meetings, it was difficult to find any info on those. But if you'd like to share if they've met recently, now would be the time. All right. Well, in that case, the last box to check is the IoT Special Interest Group. It was unclear. It doesn't look like they've met. But if anyone would like to correct me here. And that brings us to the end of working group updates. Is there any working groups that anyone has attended that we just don't have here that they'd like to share a quick update on anything interesting happening in the community? And with that, I think we will hand it over to Andrew. Yes. Thank you. Is there a way I can share my screen? Have I got permission to do that? You should. Go for it. Andrew, good to go. We can see your screen front. Great. Great stuff. I know it would turn this jumpstarting cloud agent identity, but it's very much around how we've actually spent some time with Microsoft Azure and how we can seamlessly make that experience of getting AcroPy up and running in Azure a lot better, actually. Before I go into really too much detail around that, it's a quick bit of information around who we are. Some of you may know, some you probably won't. We're a sovereign steward. We have been for about two years now. I'm actually personally the chair of the steward council at Sovereign. As IDC Global, we're an endorser, an issuer of digital identities. We kind of focus a little bit on individuals, but seems to have, as of late, been dealing a lot more with kind of like identity for businesses and trying to get businesses more engaged with the whole SSI kind of ecosystem and things around that. Because of that, some of the work we've done over the last 12, 24 months has been very much around funding things like open source initiatives. We've done a lot of work with Animo, who I think are quite a well-known organization. And one of the things we've been doing is building some kind of like open source tooling ourselves. And we built something around the Bluetooth connection list, Seren Approves, which allows basically two mobile phones to share a zero-knowledge proof or actually a full credential, if you wish, kind of like over Bluetooth. It's kind of a very cool way of doing that with mobile devices. But a lot of the work that we were doing was kind of like showing us that actually there's a ton of great things out there around SSI, but there's some problems when it comes to getting up and running quite quickly. So we found that even when we were talking to some of our engineers trying to get them to start work with us as part of their onboarding process, that things that I understand in the SSI principles was a little bit tricky at first, but then trying to get things up and running, especially with an acupy agent, that became quite, not tedious, but it definitely wasn't a quick, easy process. This kind of got reiterated back to us when we were talking to a number of businesses saying that, why don't you deploy this? We'll get a Docker instance. And they started to have to understand too much of the infrastructure below that. So while there's many workshops and samples around how to kind of work with Acupy and kind of embrace SSI, getting the agent up and running needed a bit too much domain knowledge, information to really understand the workings of Acupy. We've all been engineers or we know engineers. They like to get things up and running pretty quickly, right? A proof of concept. They want to do that as quick and seamlessly as possible. So how could we jumpstart that? And the reason why we ended up doing this work with Microsoft Azure was more to do with actually, when we started looking at certain business segments, and my background was originally or is still very much in financial services. When you get to sort of regulated businesses, they don't want to really look at on-prem anymore, but they're looking at certain cloud providers and certain infrastructures that they can leverage or platforms within those cloud providers. So we've got very much some very firm feedback, shall I say, saying, look, if this works in AWS and I can just deploy it or in Azure, great. Now Azure seems to be more of a platform of choice for financial services, and it does give you more of that platform as a service kind of experience. So we've kind of wandered our way into how do we get occupied deployments up and running as a managed application as easy as possible for anyone in the community to use, but on that Azure infrastructure. And the way we've done that is we've built something called an Azure Managed App. You may know it as an Azure Container Application if you're familiar with Microsoft Azure. What it allows you to do is to actually deploy it is like a black box. So it feels like a black box agent. You don't need to see any of the infrastructure or any of the workings underneath Acupyre. It's downloadable from the Azure marketplace. The configuration that you require of that is actually the same stuff as you would see in Docker, but it's just presented in a very Azure friendly or Azure singlass way. The underlying infrastructure at that point is then administered by Microsoft, so they'll maintain the scalability of it. Make sure you've got that elastic scale up and down, the resilience, the performance aspects of it. And if you have any problems with it, as we as IDCrypt global can go in as an administrator and have a look at if there's something underlying wrong with your agent. But apart from that, it's your agent. It runs in Azure. It's in your subscription. It's in your tenant. You maintain it, you control it. It's just there, right? If I just stop sharing this screen and then share a different screen, I'll walk you through. Actually, I'll do a deployment, right? So we'll actually go through what it looks like in Microsoft Azure itself. Bear with me for a moment. Yeah, so I think everyone can see the screen now. Yeah. Yes, looks great. Great stuff. So I'm just in my Azure subscription, my tenant, and there's the usual things that you can see here. But if I just draw you straight away to the marketplace. So if I go into the marketplace itself, you then get presented with, well, you can browse all of these things. But these are basically thousands and thousands of services or components and tools that you can add into your Azure subscription and download into your tenant. What I'm going to do is I'm just going to quickly search at the top here for what we call as the IDC agent. Let's close that. And then you get this IDC agent available here. So you can see it's an Accombi compatible cloud agent. It's actually just pure Accombi at this particular point. We do have other agents that we've also badge under IDC agent. So you have to be a bit aware of which one's what. But yeah, you're looking for the Accombi compatible agent. Click on that. I get the kind of like standard as you're feeling, right? If I was downloading SQL database or downloading any other component from Microsoft, you get the same experience. So I can have a quick overview and read through what am I actually looking at? What am I deploying? There's some plans and pricing as in how much is it going to cost me to run on the infrastructure? What is Microsoft going to charge me for the privilege of leveraging this software and technology? And there's some usage and information support. So you can go to our website. You can call us for support. And there's some other categorizations around the service itself. As I said, you're looking for a particular addition. It's the community addition, which is your pure Accombi, the latest version. And I'm going to press create. And when I come into the creation here, this is kind of like, well, this is a deployment template essentially. So what we're going to do at this point is just go through the basic setup. So the subscription I've got, that's my Azure subscription find the resource group. Now I can actually create a new one or I could select one from an existing resource group. So I'm just going to grab Andrew's test to be honest with you. And then if you're familiar with Azure, if you've got your component available in a number of regions, you can select which regions you can deploy into. Now we've decided that actually you can deploy this anywhere in the world. So I'm in the UK. If I want to select UK South, that will be the Azure region that I select. For on the East Coast of the state to go East US. But you can see all of these different regions that Microsoft supports. And therefore our IDC agent or the Accombi agent itself can be deployed anywhere you want around the globe. And we'll leave that as East US. And application name, whatever you want to call it, right? I'm just going to call it my IDC agent. So you can get a little green tick. So I know that actually this particular part of configurations are great. And then I carry on when I get into the agent and the vault. So we call it a vault. And it's just funny enough. It's just a bit of marks, you know, terminology that we've kind of landed on when we spoke to some regulated businesses, they didn't like the term wallet. I don't know why, but they kind of feel it's not appropriate for something that's sitting in the cloud. So we just rebadged it as your vault as opposed to your wallet. I can select the sovereign network we've set this one up for. So testnet or mainnet and then leave on testnet. And then you'll notice I've got these little information tool tips that give me some information if I'm very new to Accombi and understanding what I need to put in these configuration. So a little IDC, sorry, a little agent, agent label. So I'm just going to call it my IDC agents. And then you've got the seed. Again, this is two of your tool tips say exactly has to be 32 characters long. I'm just going to go grab one or create one over on another screen. And then my API key, again, little tool tips going to tell me exactly what that's for. As you can see, this is all to try and make everything as easy as possible. You know what I mean? It's a user interface. There's no command line prompts. We're just trying to keep everything as simple and as quick as possible. Your vault name, what do you want to give it as a name between three and 30 characters long, whatever you want. I'm just going to call it the IDC agent vault. And then a vault key. I don't know. I'll just grab one here. Obviously, I've managed my passwords and stuff a little bit better than I'm doing right now. And then I'm going to provide a password for my admin. And I'm going to confirm that. OK. So the little green ticks mean I've basically passed the initial validation that these were valid, valid inputs or parameters for configuration. Everything looks great to me. So I can press next. And then you'll see some information around kind of like your subscription who owns it. So Lauren Woolton actually is the CEO of IDCrip Global. So everything's in her name at the moment. My contact email address there, my number. So the pricing information here is how much is yours going to cost you to run that as a managed service. So that's for your AKS cluster or your Flex TV at the back end. We're not using Postgres, but use Flex and all the infrastructure behind that plus the IDCrip managed service capabilities there. So we've already seen a little bit of a disclaimer about co-admin access permission. So this is kind of like break glass. So we don't access the infrastructure underneath. So we can't get into the wallet itself and start looking around as IDCrip Global. We can't do that. But we can request kind of like permission from the subscription and the tenant owner if there is actually a requirement for us to do that, in which case it's kind of like a break glass process that would then allow us to access it and have a look. The reality is we wouldn't do that, bro. Some final bit of information, just confirmation at the bottom here. So here's the basic information that I put in on that first screen. And then here's my agent of bought information that I put in. I'm all happy with that. So I can just press create. And then your notes in the top right of the screen starts to initialize my deployment. So this will actually trigger off with deployment and then we jump around and you start to see the deployment in progress. So that's actually deploying into my Andrew test resource group. Now it'll take a little while to deploy it, but once it does, this screen gets replaced with kind of like an IDCrip logo. There's some brief information around what does the managed service mean to you, as in you don't need the main specific or specific information around how this this ACAPI agent works at all. You can rely on that being run by Microsoft and IDCrip in the background. The last little things to bring your attention to and I jumped back to the PowerPoint actually whilst this is deploying. Yep. So you can see that it's just part of that managed application. There's the agent resource. And that'll take probably between 10 and 12 minutes to actually go through deploy, finalize everything and deliver what we call the outputs. So I'm just going to jump back to presentation. Where is it? It's good. So flip screens again. Benefit of multiple screens. So actually skip the slide really. A quick recap really. All we've done is we've found the IDCrip agent in Microsoft Azure, the marketplace. We've selected that. Gone with the community addition. As I said, it takes between 11 and 15 minutes to actually deploy and that's with all your parameters and everything's up and running. You don't need to worry about the underlying infrastructure. So you can just focus on building, building your software, your components, learn about SSI, run some of the workshops or things you's finding in GitHub and basically get up and running very, very quickly. The thing to bring your attention to, obviously we went through the configuration on the left, but on the right here, is once it's deployed, you'll see as a resource group, you've got your overview, your activity log. You can set additional control parameters around who can access that. So that's your access control management, authorization. There's a ton of the usual seamlessly integrated Azure stuff, but the key one to bring your attention to is your parameters and outputs. So the reason I say that is that once your agent is deployed, you need to know where the port is for your DITCOM communications and you need to know how you can access the admin API. And that's kind of randomized based on where it's deployed. So once it's deployed, it will give you the full URI for the admin API and how to access that as part of those outputs. So you can quickly go to parameters and outputs, see all the parameters you originally put in, and then you can see all of the outputs there that allow you to basically get up and running and utilize it. The final thing to say is obviously I've gone through that very quickly as kind of like get up and running. However, if you're actually looking to do this as more production based, you're just likely to lock it down considerably more with the access control functionality. But that's all seamlessly integrated into Azure. So if you want to create a VNet around how you access the admin API and only certain Azure service functions, for example, can access it, you can tie that in very quickly in the same way you would do with any other piece of Azure software. I don't really want to bore you guys and carry on and go back to the screen where you're just waiting for something to deploy it. So all I would say is if there's anyone who wants any information on this, there's an email address here at the bottom where you can reach out to me directly. We do have other additions of AcuPy, we call them IDcript agents, but it's basically AcuPy with a number of additional proprietary plugins in there. Some of those we're open sourcing in the next couple of months and some of them are a bit more proprietary to solutions that we provide to some customers. So if you discover those in the marketplace, it's because those customers download it and use it specifically for their use case. I'll stop sharing and say any questions or I don't think somebody didn't understand or want to go over again more than happy to discuss it further. Tim here, I'm curious as to what those additional plugins are in functionality above the community addition. I looked at your website, it wasn't clear to me. I just wanted to take a brief overview of which ones you're applying to open source. There's a couple in there. So for example, we have somewhere we're starting to build a plugin that will take files that you've got and encrypt it based on your digital identity, whichever did you wish to allocate to it and that then hooks into something like a Microsoft One Drive or Google Drive and therefore you can store those files encrypted at rest using your digital identity that's been stored in your wallet or in your vault. That's one we're looking to probably open source once it's gone through the final beta testing. We have some other stuff that's not on the website actually that's proprietary to customers who wanted certain things added in. Some of it is just basic stuff like, okay, we want to know how many times we've hit this particular API within the AcuPy agent. How many times have we decided to run through and we've built some plugins to just pull that out and extrapolate that into like a data lake and for business intelligence. So we probably wouldn't open source that stuff. It's quite proprietary we're charging for that and it's only one or two clients are actually using it but the stuff that we think has got more value across the community we will definitely be open sourcing. The final one I should say is we're starting to do something called AMP which is Authentic Media Protection so we've got some work we've done around that. We're using DITCOM as part of the way that you can verify media files and we are open sourcing the entire verification library that we've built for that and that will be available once we've out of our Early Access program so as soon as we've finished that with a number of content creators and companies we will open source that verification plugin. Thank you. I'm just sorry, one quick follow up. Do you have endorsement in your Azure deployment? Yes, we are not in the community edition or well whatever is in the community edition but we do support endorsement but we go through a bit of a process and try to understand who we're endorsing so we do some quite enhanced due diligence on them so that if we do endorse them and give them endorse a right so to speak that we know exactly who is right into the ledger that we have endorsed so we're not just going we'll endorse your where you go there is quite a process that we go through. Thank you. Go on Brett, sorry. So out of curiosity are you employing vector technology at all in this? Vector technology you know like mathematical physics context you know magnitude, direction that kind of technology or no? No, no, no so this is purely occupied that you've seen that we're deploying there so we haven't really tinkered with it at all it's kind of been made the integration has been made into the Azure marketplace and into your Azure tenant and the way that we do that and then we provide the managed services underneath to make sure that it stays running and scalable within Azure. So that's all we've really gone through. Okay, thank you. Do you have insights into why the word wallet wasn't very popular? Yes, so we spoke to actually we spoke to a credit union, a couple of credit unions and I think there's about five of them came back and said that wallet to us sounds insecure it just doesn't sound like it's something that should be sitting in the cloud it sounds like something in my pocket or on the phone I don't secure, I don't really visualize wallet as a meaning security so they kind of got it for interoperability and some of the things we discussed they just didn't like it so we changed ours to vault and funny enough the people who objected at risk let it go through. So I find it quite almost childish but if it's a bit of marketing and a bit of spin then fine so we've rebranded everything to vault instead of wallet. Yeah, that's really interesting. I think when we start talking to regulated businesses it's quite funny because the people who make buying decisions aren't very technical and therefore they base their decisions a lot on perception and some of their perception I'm trying to be polite here some of the perception is maybe not from recent technology it's from slightly older technology so when they hear things like vault they think of a safe with a big lock on it so to speak and it's really secure and protective and great that's what we like wallet I think is saying you can just open and pull your credit card debit card out so it's just that kind of association of words so we've played and we've found the vault lands very well but wallet doesn't. Yeah, that's interesting. I mean it makes sense. Most of us have probably lost a wallet at one point or another and can't really get it back so yeah that's interesting. I was curious as well about the co-admin access permissions could you just explain again what that means and you said that you also can access the admin API as a user? So no, so as ID Crypt we cannot access that right so all we see is the underlying infrastructure as in what Microsoft presents back to us so by default when it's deployed into someone's environment we can't see anything we just know that there's an agent that's been deployed at say you know John Smith's company that's all we see and we see a health status that's it so we can't really do anything with it apart from monitoring that health status. The co-admin does allow us though to ask for permission so if we go back to John Smith's business and say we believe there's something wrong with your agent do you want us to look at it they can actually say yes they give us permission and Microsoft essentially then allow us at that point to look at the underlying infrastructure so we could have a look at if you're running Postgres or Flex in our case look at that particular database or you can look at the logs we can access those things but without that break class permission we don't have any access at all. Likewise you as the company that own it you don't have any access you can see you can configure it in terms of security you can figure it in terms of your outputs and things like that but you don't know what actually makes the underlying infrastructure so if you come and see the agent deployed it just presents itself as IDC agent that's it you don't see the resource groups are underneath it so you don't see Postgres you don't see AKS clusters you don't see the network you don't see anything you just see the IDC okay we've actually found that that adds another layer of security funny so if you think about bad actors with inside an organization if they have permissions to get into into the vault or the wallet and start poking around they could actually start seeing dids they can start seeing a lot more information they can access proofs that have been shared in the past everything else right but because it's presented itself as like this black box no one has that access so you as a company that's using it you don't have to worry about bad actors because they can't get access to it likewise we can't access it because we haven't got the break glass Microsoft doesn't access it themselves because they don't know what it is they just see it as a bunch of AKS clusters and other things so that means that there's an additional layer of security that is actually quite helpful when you start looking at regulated businesses yeah interesting gone Brett so with regards to data analytics what would be the functionality with the data analytics in terms of what we can collect yeah so if we want to collect analytics let's say from a plugin that we've added to an agent it has to kind of like we call it call home so it has to send the analytics either out into their own tenant into like a data lake or it sends the analytics out back to a permissioned kind of like tunnel so we can't see too much information inside well we can't see anything inside the agent so if you create analytics and you store it within ACAPI itself no one can access it so you need a way of pushing that information out so in the plugins that we've looked at or we've put together we've pushed that out into data lake or into data bricks in Azure or we've actually sent it back to ID crypt itself for a standard virtual API that's been permissioned and allowed to connect to that endpoint only very nice how does the process you walked us through differ for individuals versus businesses it doesn't at all so that process is exactly saying sorry when you say individuals trying to run ACAPI yeah like you said at the beginning that you serve both individuals and businesses so I guess individuals who are your your customers your users yeah so individuals if they're engineers and they want to get an agent up and running it's exactly the same process the billing looks slightly different to them because Microsoft builds individuals different to corporates so that's quite interesting likewise if you're a corporate on Azure and you have something called an EA agreement you kind of pay for stuff up front and then you have three minimum spend with Microsoft which your agent then becomes this becomes free it disappears in terms of a cost because you've already pre-committed costs across the wider Azure infrastructure that you utilize we also service individuals as in we're just finishing off a mobile application like a wallet again it's called a vault for us and that's basically your SSI based wallet we've signed to try and make it compatible with the EU stuff that's coming out obviously us being from the UK we're looking at that though I'm not a great fan of what the EU is doing so we've started to put that application together ourselves and our wallet we're kind of based it around a high level of confidence in an individual's identity so we don't allow people to just self-attest to start you have to have government based documents before we'll issue you an identity into that wallet it's a standard SSI wallet you can use it in any way you want anybody else's credentials that can come in and out the app is fine but the identity that we issue is kind of like that high confidence level and then we tie that into our experience with financial services so we build a digital identity risk profile off the back of that that can be shared as credentials or as a service base if you as a user wish to share that the ultimate benefit there is that we believe if you do that you can then go to bank accounts and open them correctly because the risk profile is actually more important than the UK YC believe it or not Interesting, thank you and that app should be out in the next couple of or actually going to the States right so it won't be out in the States for a while it's just released here next Monday, right? Nice, that's exciting Yeah and part of that is also so when I said businesses and individuals I mentioned the Bluetooth open source tooling that we did the SDK we do have a business app that's called just verify that allows your corner stores for example to face to face just verify your credentials or your age, so you can do age verification you could ask for your password verification if you want to for the purposes of voting and that goes over Bluetooth between the two devices we're just starting to showcase that next week here in the UK hopefully we'll get some traction but it's quite it's quite slow trying to get people to understand some of these concepts Are the verifiers are the corner stores set up to be able to verify that information? So no, but they can download the verify app and it's free and they can have the phone and then we're going to try and get them educated and understanding how to do this if you're not charging for that what we've made sure is services that are related to like an audit behind that so if you had an investigation did you sell cigarettes to someone under the age of 18 at least you could prove for an audit trial that actually they did the right checks and everything else so we would sell them the service not the capability if that makes sense right, right yeah that's awesome and that's what we hope to do in the next couple of weeks if you've got individuals and businesses in time and together it's all good because you have that chicken and egg whereas businesses say we'll use it if you've got millions of users who've got your app and likewise if you give it to users they go well I can't use it anyway I'll say it's pointless you deal with that that kind of nuance anything else I can go over very quickly or anybody want to recap just out of curiosity did the deployment complete out of curiosity it is still running at the moment but because you guys I shouldn't think you'd want to see it I did just stop it oh all good but yeah it just deployed I can show you what one looks like actually can I show you what one looks like yeah so I've stopped it so it's gonna save value to provision but let me just share this screen so I can show you how it presents itself yeah so this is one I've just stopped actually I just terminated a few seconds ago but if I go in so obviously this is palatable vision because I've stopped it but that's how it presents itself so that's all you get really you get this little logo what was application to blur some information at the top here and then your parameters and outputs if you clicked on that I mean the outputs have stopped because I've terminated the deployment but you can see here's my original parameters that I put in and then the outputs as I said that would have your admin URI and other information but that's where you the rest of it is all just standard Azure that's integrated to it so if you want to look at your internet access you want to add some roles and role assignments who can deny you know all those sorts of things you can do that through the standard Azure interface but yeah your parameters and outputs is the key point they're good yeah thanks for showing us that so guys thanks for having me if that makes sense I know I've kind of run through it very quickly if anyone's got any questions in the future or anything I'm happy to take those whenever and we're having to try and publicize a little bit more about some of the open source stuff that we're pushing back out into the community we haven't done a great job I don't think doing that because the bluetooth component has been there for probably six months now I don't think anyone's aware of it nice yeah that would be great thank you so much for joining us this was an awesome demo and presentation and Andrew if possible you could get Shara myself some links about idcrypt and the solution so I can make sure it's included in the youtube video this way folks want to find out more they can they can get in touch I'll ping you that later sounds great yeah and if you'd like to send me the slides from your presentation too I can add them to the meeting page for those who are watching the recording and want to follow along as well yeah I will do great thank you so much lovely thanks for having me I'm going to drop off just because here in the UK it's quarter to five and you can drop the hint I've got four kids so I can hear them in the background noise and some of that noise is dad wears mine then so I'm going to go and play daddy game really great to meet everyone and I'll share that information as soon as I can great thank you so much Andrew lovely thank you alright well that does bring us to the end of our meeting today thank you everyone for coming and I believe it was streamed live to youtube so if you missed anything or want to rewatch you can find the recording there sounds great thank you so much everyone thank you everyone later thank you