[MUSIC].
>>In the next minutes, we will look at
the Azure Stack multi-tenant subscription delegations.
So wait for the Azure Stack operator to actually
get rights inside the tenants subscriptions,
as well as a few options
for creating a support ticket in the CSP context.
Here we have an Azure Stack ASDK,
which is registered against the AzStackReseller1 AAD.
So this was used to provide the identity of the SDK
and we use that AD to configure it.
I've also registered a couple of new tenants.
So this system has been enabled for
multi-tenancy and then we onboarded two tenants,
one it's called AzStacktest1,
and the other one is test2.
You can see here the both tenants being separate resources.
So you have, this is the test1,
and you also will see
the AzStackReseller1 which is our initial AD.
So the one which we actually use to log in Azure Stack.
So the same things will be visible from PowerShell.
So if we go back here to
the PowerShell and we connect it to Azure Stack,
and then we run.
This "Get-AzureRmResource",
and filter by the directory tenant resources.
You'll see these three resources, all the initial,
AzStackReseller1 and then the two test domains listed as well.
What I've also done here was to create a public offer.
So if we go to offers,
and you'll see here the TestOffer1,
and this is created as public offer.
So anybody can use it to create new subscriptions.
We've used a number of quotas and plans to create these offers.
So we have them in this TestPlan1,
and if we look at subscriptions we'll see two subscriptions
already created based on this offer.
So we already have it in use.
Now if we go to resource providers and we double check the quotas,
we can see each of the specific settings.
So we have a custom quota built,
and we have inside the specific settings for each of these, right.
Now moving forward and switch over to the tenant directory,
you'll also see that we don't have any subscriptions created here.
We could do it but we haven't created anything yet.
So if we look on the subscriptions,
you'll see nothing is created here.
So the two subscriptions you've seen earlier were actually created
on our test one tenant.
Now if we were to connect to their tenant directory,
so we would connect - this would prompt an error saying that
the user is not actually recognized by that tenant.
You don't have any rights inside that tenants space.
So this is one of the differences between
the Public Azure and Azure Stack.
On Azure, whenever you do admin on behalf of,
you would be connected to the actual tenant space,
and you are the owner of
that subscription, Azure subscription.
So on Azure Stack,
the subscriptions belong to the tenants themselves,
which means you as a CSP provider you will need to be
given rights inside that tenants space.
Once you are given rights,
you will need to be assigned rights to the actual subscriptions.
So to take a look at how this would be done,
we will need to go AAD of our test1 directory.
So we will need to using the admin from our test1 directory,
we'll need to connect to portal.azure.com,
and then select the Azure Active Directory.
So in here, we will invite
the admin user of our Reseller1 directory.
So this is the CSP directory.
So we'll need to paste, well we need to paste the correct one.
You can see I've pasted the test1 here.
So we'll need to pace the Reseller1 admin.
Once this is done,
an invitation will be sent to that user
and they will be added in the Directory.
So this will go out,
and once it's sent,
we can go back to our Azure Stack portal.
Under subscriptions we can
delegate rights to that newly added user.
So if we go here to "Access
Control" and we select let's say an "Owner",
we will find the new added Reseller1 admin.
So we will save it,
and now we can delegate rights to this guy.
There's an important trick here though.
When we go back to
our Reseller1 user and we try to do the same thing.
So we will try to connect now to
the tenant of our test1, or the user tenant.
There's an important piece missing,
so this will fail and the message will be that
the user doesn't have rights in there,
it does not exist.
Although we added that and we all also gave him permissions,
the user itself is not confirmed in that directory.
So an e-mail is sent out,
and when the e-mail is sent out,
the user will need to do,
there's a link and the user clicks on that link,
and the confirmation is made.
Then the user is properly
added to the tenant directory as a guest.
So if you don't have an e-mail,
there is one way to do it.
We will need to go back to the AAD of our tenant,
and resend the confirmation.
So if we go back here and we select the Reseller1 admin,
you'll see a resend invitation link.
Once you click on that,
it actually will give you
the link which is supposed to be in the e-mail.
So if we don't have an e-mail,
you can just paste it from here.
Now we will go back in the context of
our Reseller1 paste the link,
and this will prompt Welcome to AzureStackTest1.
So this is our tenant.
So we say "Next" and now we are
properly added to that guest directory.
So at this point,
if we switch back to Azure Stack,
the user portal in Azure Stack,
and by using our Reseller1,
we connect to the tenant of test1.
You will now see under subscriptions, yeah here,
so under subscriptions you'll see you actually
have a sub one in there.
Okay, so we were added as an owner here,
so we can do anything we want.
So to give an example,
let's reach back to the test1 directory and
go under the Azure Stack subscriptions.
Under subscription two, lets give our admin Reseller1,
let's give it rights as a let's say a reader.
So we select "Reader" we select our Reseller1,
and add him as a reader on the subscription.
Going back to the Reseller1 context,
we will just refresh the window,
and now we will see that
the two subscriptions in there, all right.
So at this point you're able to manage
both subscriptions one as an owner, one as reader.
Azure Stack provides an integrated support experience
which is consistent with Azure.
So I think it will be open in the same way,
and regardless of where you open it it gets solved.
Say it's a hardware issue or software issue,
it would be sorted in the end.
So it doesn't matter who you're reaching out to first.
Of course it would help if you're able to
identify where the issue
is coming from to directly target that respective partner.
So say it's a problem with an update process,
you would probably reach out to Microsoft directly.
There are multiple scenarios for support and we
have published a document
which goes into more details around them,
and you can find that on the EAI site.
In the following examples,
we will look at a CSP contexts and
what are the steps to actually open a support ticket.
In the following example,
we will use AzStackReseller1 which is
an owner of the Azure subscription and Azure CSP subscription,
but it's not added as an admin agent on the CSP site.
So if we go to portal.azure.com, we can open,
we can go to new support,
so "Help and Support" and try
to open a "New Support Request".
So opening the requests,
you will provide the issue type.
So let's say we have a "Technical" issue,
and which is a subscription.
So we select the Azure subscription we have,
and then what service is causing that issues,
so let's say Azure Stack.
At this point, you'll be greeted with a message
saying that you need to reach out to your Cloud Service Provider.
So the reason behind this,
is that our AzStackReseller1 admin
is not added as an admin agent on the CSP site.
Although they are an owner of the subscription,
so they can manage anything inside the Azure subscription,
they're not added as an admin agent on the CSP site.
So here I am connected with an admin agent.
So you can see the partner center and if
we open a portal.azure.com,
this would be that the CSP tenant itself, right.
So if we go
under 'Support 'and we try to open a "New Support Request",
you'll actually see there's no "Technical "here.
The reason behind it is as a CSP admin,
the subscription itself doesn't have - so
the tenant itself doesn't
have any subscription in here, right.
So what we'll need to do is we will need to actually connect to
the AzStackReseller1 tenant.
So if we connect under this Reseller1 tenant,
we are also owners of the subscription.
This is a CSP Azure subscription.
So any admin agent would be
also an owner of the subscription, right,
and now if we go on the "Help and
Support" and do the same thing "New Support Requests",
and then select the "Technical" issue.
Select the subscription the service would
be in this case "Azure Stack".
Oops my bad.
Not "Batch Service",
unless you have an issue with "Batch Service".
But we wanted to open a support ticket with "Azure Stack",
and now the support plan will be the "CSP" support, right.
So if you have other support plans,
they will be listed here as well.
Now you'll have the normal problems support requests.
So this is you specified the severity,
the what is the issue coming from,
you provide some details around it and then off you go to
actually provide conduct information
and to create the actual ticket.
That's one way to do it.
The second way you can actually create
a new support ticket is through the "Partners Center",
and under "Support" you have customer requests, right.
You type the name of your tenant.
So let's say AzStackReseller1 in this case, right,
and once you click this you have an option
to create a new your support requests.
If you click on "Microsoft Azure",
what happens is and if you notice,
you'll be redirected to the Azure portal,
and you'll go through the same experience we went through before.
So the way you use start the process is different,
you will go through "Partners Center",
but other than that everything else will follow in the same way.
All right so the end result would be the same in this case.
[MUSIC]