>> Hi everyone, welcome.
I'm Saca with Patrick here.
>> Welcome.
>> And we're here to talk to you about
Azure Government, specifically for Partners.
We will start with the obvious question, right Patrick?
What is Azure Government,
then we'll switch over to how
can partners use Azure Government.
We'll get you all excited hopefully,
and then we'll tell you how do
you get started with Azure Government,
how do I actually go ahead and play around with it.
And we'll wrap up with some considerations in
best practices when you're using Azure Government.
Patrick, what is Azure Government?
>> This is a question we often get from our partners.
I think one of the first key things
that partners need to understand,
is that it is a physically separate instance
of Azure Government.
So, all the way from the servers,
to the data center,
to the actual networking and express route connections,
to the complete management fabric of Azure,
is completely isolated for Azure Government.
>> So you're saying there's an instance of Azure,
and there's a very separate one
that's dedicated to the Government.
>> Exactly. And we've done
that because the government has a set of
regulatory compliance aspects that are
required and are not met by our Azure commercial cloud.
>> And is this any government,
or specifically the US Government?
>> That's a great question.
So this specific cloud that we're talking
about in question is
purposely built for the US government,
includes our federal entities,
state local, as well as tribal entities,
and then of course,
partners or solution providers that have
solutions and that are supporting our customers.
>> So compliance is a big thing
for this cloud in particular?
>> Yeah, it really is. The federal government especially,
as well as the state,
have a set of regulatory compliance aspects
that far exceed what we
see in our commercial environments.
>> So you talked about Azure,
this is a separate instance of Azure,
let's give people a little bit of context,
let's talk about the scale of Azure,
what are we talking about here?
>> Yeah, I think this is a very good question Saca.
One thing to start with is I don't
think people realize that we're
one of the largest fiber producers in the world.
So we've got a lot of fiber that connects,
over 42 Azure regions,
across 100 data centers,
that contains millions of servers.
>> W ell, so are all these dots in
this diagram that you're showing
us the different regions?
>> Yeah, these are the regions,
lot of our regions have
multiple data centers with the servers and then itself.
Also keep in mind that this isn't
just compute, like a VM.
It includes our infrastructures and service,
our platforms as a service,
and then our first party finish
sash solutions like Office 365 and EMS,
run inside these Azure data centers.
>> That's pretty cool, so let's zoom in a little bit into
specifically the US Government version
of this diagram. What does that look like?
>> Yeah, so today we have
six regions that are in production.
We've got four that meet what we call we'll
talk a little bit more about compliance here shortly.
Four that meet FedRAMP High,
Level two and four.
Those are out there today we've got a pair on
the East Coast and a pair on the west coast,
and then we have a dedicated two more regions
just for our Defense Department.
The Defense Department has higher requirements,
that meets what we call IL-5, and then recently,
we announced what we call Azure Secret,
which will be coming in December,
and that meets what we call IL-6 standards for the DoD.
>> Azure Secret, I guess not so secret now,
since we have been talking about it.
>> That's right.
>> So, and what's in this diagram
the express route locations, what is that?
>> That's where customers can actually connect,
they're like a meet me points so that they
can connect their network to ours,
and I think it's another important point of isolation.
There's no public traffic that goes
on these so some of our competitors might
have their commercial as well as
a government customers on it.
When we talk about
isolation with Azure Government, everything.
Not just the servers and the data center,
but also all the network traffic
has its own circuit and it's dedicated.
>> So we've been zooming in from the big map
with the whole diagram of all regions
and we looked at the US.
I think you also have a picture of what
an actual data center looks like, right?
>> Yeah, I do Saca,
and I don't think people always can
understand what we mean by hyper-scale cloud,
this is a just one data center.
It's actually one of our Azure Government data centers,
this is what it looked like two years ago,
you can see what it looks like a year later,
and you can see that we've added more data center,
compute storage, and networking.
And then finally, you can
look and see what it looks like today,
where we've actually paved ground to expand it.
It really puts it in perspective like
how big we're talking
about here when we mean hyper-scale cloud.
And this again, this is just a single data-center, right?
We've got hundreds of these.
>> And I won't even go back to the first picture.
Is that truck there?
>> That is. That's an 18-wheeler.
>> Double that up and double that again.
>> Yeah.
>> Pretty big. So we talked about the scale,
let's talk a little bit more
about compliance and all that's
a hot topic for when it comes to government,
what does compliance mean?
Give me the next level of detail here.
>> Yeah. So, looking at
the slide you're going to see that we've
got compliance offerings across global,
across many different industries
but we're going to really zoom in
on what we're doing specific
on the Azure Government side.
So if you start out with FedRAMP,
the Azure Government cloud
meets what we call FedRAMP Moderate,
FedRAMP High, DISA which is
a compliance aspects related
to our Department of Defense customers.
We meet both L2, L4,
and L5, and as mentioned earlier, with secret.
We'll also be getting there in December with L6,
and then we have a certifications called CJIS,
that we'll talk a little bit more
about in the next slide,
followed by IRS 1075.
>> That's a lot of certifications.
And honestly as a more technical guy,
I'll trust you that there I infer to them,
I know they're important, but
I'm glad Azure does it for you,
because I don't want to have to worry about any of that.
>> Yeah, it's great. And we've got a full site,
will have a reference to this later in the deck.
We have our Azure Trust Center which
details all these different certifications,
and all the corresponding documentation approves them.
>> Now you've talked about how there's
so many services involved in Azure,
I know those first-hand.
Well, how's that apply from a compliance perspective is,
is it just Azure compliant,
is it each service compliant,
how is compliance work for each service?
>> Yeah, that's a great question.
And I think sometimes what you'll
find with our competitors,
is they'll have a FedRAMP certification but it may
only apply to things like they're virtual machines.
With Azure, we've got 42 of
these services that have FedRAMP compliance today.
And every month, we're adding more and more.
We actually have a team in house
whose full time job is to work with the FedRAMP JAB,
to work with our service engineering teams,
to make sure as we build these service,
they're compliant by design,
so that we can get them FedRAMP
as soon as they become available.
>> So that that's fine level of detail and
granularity than I think
not a lot of people are aware of?
>> Yeah.
>> I also heard that CJIS is tricky as well,
there's something about it that's
different from the other certifications?
>> Yeah that's a good question.
Whereas FedRAMP applies to all federal agencies,
CJIS is more at a state level,
and we have to negotiate with
every state to get CJIS compliance.
Today we cover 70 percent of the population,
we've got five more states enqueue,
this is something that we continually work on.
And the really important thing about CJIS is
if you're doing stuff with law enforcement data.
So let's say you're ingesting
body camera data from a police officer?
>> That must be a lot of data?
>> Yeah, it's a lot of data,
it's a hot topic right now, and as partners,
those make up a big part of
our software vendor ecosystem that run on Azure,
where they're ingesting that data up into Azure,
CJIS is the compliance certification
that allows them to store that data on Azure.
>> So, that's definitely where you
want that sweet combo of
hyper scale cloud and compliance?
>> Correct.
>> So Pat, you've
explained a lot of things about compliance,
let's talk a little bit more about adoption.
What is Azure Government adoption looked like these days?
>> Yeah, so this Azure Government Cloud
has been around for a few years,
and I'd say we've got really strong momentum right now.
All of our federal cabinet agencies
are using Azure Government.
All branches of the military across
the Department of Defense are using Azure Government,
were ingesting a petabyte a data a week,
and we've got a lot of other Iot,
as well as Police and Public
Safety solutions especially on the partner side,
that are really leaning in and
moving everything they have into Azure Government.
>> That sounds like there's a lot of
opportunities to help make a real impact here
with the government by helping partners connect with
them build solutions that can make a difference I guess.
>> It is, because if they were to try to achieve some of
these certifications that were
reviewed on previous slides,
and not only is it millions of dollars
just to achieve them,
but they've gotta maintain them.
When you start talking about
one certification is one thing but,
if you've got a solution where you're trying to
serve a state and local governments,
the Department of Defense,
as well as the Fed civilian agencies,
you can spend a lot more on compliance
than you might ever make,
so it really helps them address this market.
>> That's good. So there's a lot
of opportunity for partners here.
I think we should now talk a little bit about
how can partners and who is
meant to be using Azure Government.
>> Let me kick that off with you.
We talked to a lot of partners everyday,
and I'd like you to kind of dispel a few miss here.
Tell us like, who is it?
What kind of qualifications?
What are the requirements?
Do I need to have a top secret
security clearance in Azure cloud?
>> Yes. A common myth.
I'm glad to be the expert for ones now and
I was asking all the questions now I need answer a few.
So, Azure Government actually,
there's a lot of myths around who
cannot use Azure Government?
The first and most obvious one is of
course government customers agencies,
state local, all the good agencies you've
talked about are meant to be using Azure Government.
But this is also meant to be a solution for partners.
Partners can come in two different ways.
One is if you're either providing services
or solutions to the government
you get access into Azure Government.
The other is if you're dealing
with any government regulated data,
which generally is tied into
the fact that you're providing services to them
but if you deal with
any government regulated data
then Azure Government is also for you.
>> Got it. So it's also safe to say
that without these partners in here,
or that these partners really
enriching the ecosystem for our customers.
>> Yes, of course. That's a trend we're seeing
the government tech is not their thing,
so they generally rely on
partners that do know tech very well,
to partner with them to figure out
the mission and go address some real problems.
So it's a great partnership so to say
between our partners and the government.
>> Great. So let's talk a little bit about volume, right?
We talked about momentum and we talked about
the customers using Azure Government
but give us some idea.
Do we have a lot of partners in here?
>> Yes. Partners in Azure Government is not new.
We hope with this video you guys will be more enticed,
and we'll have more but even today we have
500 solutions that are
available through the Azure Government Marketplace.
The Azure Government Marketplace makes it super
easy for a one-click experience where you just go in,
and select the solution click on it and you
get that solution up and running
without having to configure it yourself.
So it makes things very easy for
government agencies and other partners
to leverage these solutions.
The other thing is we have 170 Cloud Solution Providers.
I don't know if you want to cover those.
>> I think the Cloud Solution Providers are really
important for the ecosystem.
This obviously allows a partner that might be
a system integrator to bundle their solution with Azure,
and not only manage the solution on behalf but they're
actually reselling Azure tools
the end government customers.
So, that helps with their top line
and they can make margin on all that.
>> We also have partners that are running
their solutions using Azure Government directly.
How many of those do we have?
>> I think there's around 350 total. So
>> That's a big number.
>> Yes.
>> One of the things we should deep dive
on is the next level of this.
We've talked a little bit around the high level,
these are some of the numbers,
there's these types of
partners and how they get involved.
Let's go a little bit more in depth as
to what a Software Vendor,
that's type of partner and a System Integrator can do.
So software vendors let me talk about those,
since I deal with those most.
Software Vendors can range
from I already have a solution that helps you
do monitoring or manager
infrastructure and they've been
doing this on-premises for a while now.
We want to allow them to connect with Azure Governments
so that their customer-base can also
use that tool to manage the infrastructure,
or whatever it does in Azure Government.
So that's the API integration
that's kind of the simplest of the integrations.
>> So should I think about that like let's
say I'm running Citrix on-prem,
and I've got too much servers,
they're about to go into life.
Could I then spin cores and Azure instead?
>> Yes. So the solution still runs on-premise,
but what you end up doing is scaling out to the cloud,
effectively what Citrix in this example would do,
is they would extend their tools so that it
knows how to talk to Azure and Azure Government,
and allows customers to also have
part of those resources spun up in the cloud.
>> Right. So I would assume that would apply
to Backup Vendors as well,
as it feels like spunk and what not.
>> Yes. There's countless scenarios for that.
Then the other side which
is one I've talked a little bit about is the marketplace.
So marketplace is easy
for partners that have solutions that
had been packaged and
install on-premise for longest time.
So if you imagine a scenario where you have
a VM that you want to go install some software on it,
what the marketplace does is it pre-installs it for
you such that I just go into the Azure Government portal,
and say I want a new X piece of software running.
Provide some basic parameters to it like
a username and password and some other configurations,
and it stands that up for you.
So it makes it really easy to use,
and we see a lot of ISBs using that.
>> That's awesome. What do I do
about licensing in that case?
>> Licensing today in Azure Government is a bring
your own license so you transact with the partner.
The partner provides a license which you then provide
into the marketplace so that it
gets initiated with the right licensing.
Alternatively, what some partners do,
is they also create trials that it's just
more for a quick and easy get started experience,
and then follow up with the government agency
for the larger scale or more serious appointment.
>> Got it.
>> The other thing we've seen is
Managed solutions and SaaS solution.
So these as you move across the spectrum from,
"Hey I'm just taking my prepackaged solution that I've
done for many years" to "I want to offer them a service."
So they don't even have to worry yes
there's the one-click experiences in the marketplace,
but in the marketplace you still need to manage that VM,
manage the infrastructure, make
sure it's up and running, patch it.
When you're going into the Manage space and
the SaaS space a partner takes care of all of that.
So the government ends up just having a URL,
or an app that they use.
They don't care how it runs in their hood.
It just happens to run on Azure Government,
so that the partner can easily
meet their compliance certifications,
and have the Hyperscale cloud to back it.
>> Awesome.
>> The other thing and I think this is
an area that a lot of interests for
the government in particular are System Integrators.
I know you've dealt a lot with those.
>> I have. >> What are those scenarios that
System Integrators generally do?
>> Yes. System Integrators can do
everything for these fair government customers.
They can do an architecture and design on a solution,
we see them creating new applications to
solve a business problem for the government,
they might go look at their on-prem infrastructure,
and provide a path to
lift and shift that stuff up into the cloud.
So anything that they've done on-prem,
they can apply the same context to the cloud.
But there's also a special set
of SaaS and we're seeing this more and more.
Where they might take a product that the customer has so
if the customer has this running
on-premise government entity and they're like look,
we don't want to really deal with this
anymore as we move it to Azure.
You guys are taking a bigger obligation as Microsoft.
But, there are still patching and operating
system updates since stuff like that need to be done.
So, we have a set of Managed Solution Providers that
then take and basically provide the end to end on that.
Kind of like SaaS,
but maybe for a custom solution
or a product that might run on-prem.
So, Managed Service Providers are really popular on
the Azure Government side and they're
turning to us for their storage,
compute and database and networking needs.
I bet these guys are itching to get their hands on Azure.
How easy is it for them to get started?
>> The quickest way to get
started is just with a free trial,
aka.ms/azuregovtrial.
You go for sign up for the trial,
you get validated and we'll talk
about that a little bit more,
and you get an account. Simple as that.
>> That's easy. So tell us about this validation.
It sounds like it might be hard,
or I'm going to have to sign some paperwork,
or the government might have to interview me or
my might [inaudible] What does this mean validation?
>> Again you're myth. No it's not that bad.
Actually is not bad at all,
it's really two buckets.
It's either one, that you're
actively doing business with the US government.
So if you already are
then this probably already sounds familiar,
you might get asked for a GSA contract which is something
again if you're doing business with
the US Government, you'll really know what that means.
You'll just provide that, you're good to go.
The other bucket is
I haven't done business with the US Government.
I as a partner,
want to make sure that I indicated I've
taken the initial steps towards doing so.
The easiest way to do that is
there's this website called sam.gov,
where you acquire a SAM ID and a DUNS number.
These are the things that we require from you,
there's other options but this is the
easiest if nothing else sounds familiar.
Where you can sign up quickly,
easily and it's free.
So, between five and seven days you'll
have a DUNS number and you'll be good to go.
You as a partner might already be registered on it,
someone else in your company has done it.
So, I would encourage you to just even first search,
and then you might already
have a record there, and you're done.
>> Good. So you're not going to take my fingerprints,
do a background check or anything like that?
>> Nothing like that.
>> Okay. All right so I think we've
talked a lot about what Azure Government is,
how is of great benefit to partners,
what it takes to basically get inside the environment.
All right so tell me a little bit about the differences.
Is this going to be, if I use a VM,
a virtual machine on commercial,
and I want to come over to gov
is this a whole different experience?
What does the portal look like?
>> The very first thing you deal with is the portal and
it's really the same thing as
commercial the only difference being the URL.
As you said before it's a separate instance
so everything is a copy and paste.
So you go to portal.azure.us which
is only slightly different from portal.azure.com.
Once you're in it, you're going to use
same portal you're using in commercial,
same experience with a few differences
around the services available.
So, while we strive to have
most services that are available in commercial,
also available in Azure Government,
some of them are in very early stages.
There previews, the engineering teams are
trying out the concept getting feedback, churning on it.
Which is generally something that government customers
are less willing to try out,
or they might try it out but not really
will use in their production workloads.
So, we do a little bit of betting
before a service is available in Azure Government,
and we understand that customers need to know what is
available in each cloud particularly in Azure Government.
So we have this website again aka.ms/azuregovservices,
where we list out all the services that are
available in Azure Government,
and for those that are on and have
some minor variations would
call out what those variations are.
>> Good. That seems pretty straightforward.
Most of the services are there,
if they're in preview or early stages of development,
sometimes they won't be but we're going to strive once
they get released to bring them into the boundary.
If I need a service that's not there,
where can my voice be heard?
How can I help you guys prioritize that?
>> Yes of course. So, even if a service is in preview,
you still want to know what you're interested in.
Partners can access our feedback forum
aka.ms/azuregovfeedback,
and go post their ideas.
"Hey I'd like to see the service."
We're showing an example where
DevTest Labs as something that
wasn't available in Azure Government,
it is available now.
So we react to this feedback.
We actually do take it into consideration
and make services available.
But not only that, having you record
your interests helps us make sure
that we're addressing the right things,
focusing on the right things,
and it also gives us a channel
to communicate back with you.
So as soon as you create an entry and as soon as we have
an update on it and we know it's
planned or this is they want to become available,
we'll go update the feedback form and say,
"Hey guys this is coming"
or in certain cases we will say,
"This is not coming here's why" so this
is our way to communicate with you guys.
We really hope you can go and put
your feet back there so we can
communicate more with you guys.
>> Awesome. Well we can have a great platform but
without great developers it's
really tough for them to really build stuff.
So tell me a little bit more,
you know we've got lots of developers
out there that are building
open source using.net and some of the standard Microsoft.
But if I'm a developer like what should I know about?
What are some of the considerations
about using Azure Government?
>> Yeah. So, it's a consistent theme
as we mentioned with the portal.
You'll see that most tools that
we have support Azure Government they
just require a minor tweak just like
the portal was from.com to.us.
If you're using PowerShell or Azure
CLI you need to tell that tool,
"Hey I'm talking to that other instance
of Azure that's not the default one commercial,
I'm talking to Azure Government."
So in the case of PowerShell the command that you use to
connect in PowerShell to Azure as
login Azure ARM account.
In the case of Azure Government you just need to
specify dash environment Azure US Government.
This is your way of saying I want to
make sure I talk to this other cloud.
And you will see something similar in other tool.
So Visual Studios and example,
there's an extension that's been created to allow you
to adapt all the options in Visual Studio,
to make sure that they have a picker for you where you
can say I want to use Azure Government.
So there's the Azure environments electrode extension and
you'll see similar things in
other tools like sequel management studio.
>> Jonas we wouldn't want to hard code
that kind of stuff as a developer if
I'm going to be working across
multiple clouds and makes it easy for me to
build my application and run it
in both commercial and the government cloud.
>> Yeah besides the tooling,
the other thing is when it comes down to
coding, billing your application.
If you're just going to build
an application for Azure Government.
Then you can go ahead and "hard
code" so to say even though it's not ideal.
But you can do that and just make sure you code
towards the end points that are for Azure Government.
Again, and I want to keep harping on this
it's a separate instance so the tools need to be
told go talk to this other instance and
the APIs you're talking to are in a different end point,
and sometimes have different API versions.
So as an example here we have if you want to
authenticate which is something
you need to do for any API,
you can login to microsoftonline.us.
Again, nothing too different
but it's a different end point.
And then once you get a token back you need to go talk to
SQL or storage or whatever it
is there's also a different URL for that.
Now, if this is only if you're doing a down at the wires,
so if you're actually going and talking HTTP,
and I'm geeking out completely here.
But if you use the SDKs then they do
this for you all you need to do is like the tools,
make sure you tell it when you
call the constructor or whatever it is,
make sure you tell it,
go talk to Azure Government.
>> Got it. But this seems pretty straightforward.
>> Yes, I mean people sometimes
miss it so if you've already built an app
and commercial our recommendation is just
throw it into Azure Government
then see where it doesn't work,
and then just go make this fixes.
All of this is actually documented in much more depth in
our documentation a KMS Azure gov doc.
So you can go check it out and we
have these and other tips and tricks.
>> Cool, I think earlier you alluded to this marketplace.
Tell us a little bit more about what it takes to
provision a virtual machine inside
the marketplace if I'm a software vendor?
>> Actually the easiest path is if
you already done everything that it takes
to provision a marketplace image or
a solution into Azure commercial,
it's literally a checkbox.
All you need to do is
and you'll see it on this screenshot over here,
there's a check boxes that says Azure Government Cloud,
you check that one, we publish and you're good to go.
This is one of the easiest things you
can do to increase your exposure,
so you can get exposure to
government agencies and
partner building solutions for Azure Government.
Now, we do get again the myths,
I'm surprised you didn't raise
this since you are the myth guy.
But you don't actually need any thing to
publish this solution so you don't have
to have US nationals,
you don't have to meet any compliance requirement.
This is really just getting
your solution out there generally
FedRAMP and certifications are done
more at overarching system level,
of which your marketplace image
is just going to be a piece.
So, the agency or
the customer might come back to you and say,
hey can you add these features
or do this thing so that it
makes it easier for my whole system to be compliant.
>> Right.
>> But the marketplace image in and of itself is
not something that can be or can't be compliant.
>> Right. So these could be full solutions or
they could be components or
building blocks like a firewall for
a network or some sort of a database,
that's unique to the government or
just something that we don't have natively within Azure.
>> Yeah, generally they are more on
the building blocks side of components,
solutions are tied to missions or businesses.
So these are bigger things that solve
big business problems and big mission problems.
Marketplace solutions are generally
more as he said networking,
firewall, compute, database, things like that.
>> Yep. >> And are part of a bigger
mission problem that gets addressed.
>> Yeah. You're kind of
building on the whole system idea, right?
So we talked about the marketplace and those components.
Let's say I am building a more of a SaaS solution or
I'm implementing a new application
that I built for a federal agency.
What can you guys do to help me?
We know FedRAMP has a lot of controls in it,
have you guys done anything to make
that easier for me as a partner?
>> Oh yeah of course. I did mention that a while ago that
as a developer I don't
want to deal with any of that compliance stuff.
So it's actually Azure Government makes a lot of
the hard decisions for you
or takes care of some of the controls on your behalf.
So what you will see is we have
this notion of a blueprint.
What a blueprint is is,
before even going to the blueprint we
have the base set of controls
that we just meet
because you're running on Azure Government.
So things that are tied to physical security
these are things that we take care of you as a partner,
an agency doesn't need to worry about.
By virtue of us being compliant,
you are also compliant in those controls.
But then there's other things that
we're not necessarily compliant for you,
but we provide the tools for you to do so.
And that's where this blueprint comes along.
The blueprint as the name implies is here's
a cheat sheet of the features you can turn on or
the architectural patterns you can follow so that you
are lined up towards
success when it comes down to compliance.
So there's two ways you can use this blueprint,
one is if you're starting from
scratch you don't have an app,
you go and look at this blueprint and either just
deploy it and start growing it into your application.
So, from the moment it's
already going to be compliant since it's
going to be falling all the patterns and practices
that we recommend for compliance.
And then you just extend it with
your application and admission needs.
The other option is if you already have
a solution you can use a blueprint as a reference,
and when you look at a control that says you need to
meet encryption address you
can look at the Blueprint and say,
Oh here's how that control is met,
let me mimic that in my own application.
>> Sounds like you make it super easy for our partners.
>> Yeah, I mean, compliance is never
the easiest thing in the world
but we certainly make it much easier.
And beyond that we actually also
have resources to help you.
So if you go to that blueprint link
you can get an email so
that you can ask questions and say,
"Hey Microsoft, how does
Azure Government help me meet this control?
Or I have this application here's what I'm doing,
here's how I'm using things,
help me meet compliance."
And we can help you with that since this is something we
do for 42 services.
So we're constantly getting more services compliant,
your solution is similar to one of our other services
another service or solution that
runs in Azure Government that
we can help you get compliant on.
>> Oh so you're saying kind of this blueprint program
and this blueprint team it's
the same ones that are actually getting
our first-party Azure services
through the FedRAMP process?
>> Yeah, that's where it all
originated we started doing this so much
so we said sounds like this is
something that everyone would benefit from,
so now we're making it available
to partners and customers.
>> All right, so we've talked about a lot of stuff.
I'm sure these people want to kind of keep up.
What kind of resources do we have so that they
can stay up to speed on Azure Government?
>> Yes, so we have this cheat sheet on the slide,
we've talked about most of them.
The only other two ones worth calling out is
The Blog where you can keep up to date
on the latest and greatest in Azure Gov.
And Stack Overflow for developers so you can ask
questions and hopefully even get
answers before you even ask the question.
>> Well awesome, I want to thank you for your time today.
Hopefully at the end of this presentation you guys have
a very good idea of what Azure Government is?
Who can be in there?
What are some of the best practices?
And how you can keep up to speed with
Azure Government and all the progress
we're making? So thank you.
>> Thank you.
For more infomation >> 2 HOURS The Relaxing Meditation Music、Water Sound、Sound Therapy、Music for Yogaヨガ音楽、ヨガヒーリング音楽、妊婦 - Duration: 2:13:59. 
For more infomation >> What product do you use for your hair - Duration: 2:52. 
For more infomation >> Mackinac Bridge Walk Options for 2018 - Duration: 2:17. 
For more infomation >> OneDrive for Business - Duration: 0:17. 
Không có nhận xét nào:
Đăng nhận xét