TechNet

Thursday, 10 June 2021

Working With Windows Admin Center In Microsoft Azure

 

Microsoft Azure has another new feature called Windows Admin Center (preview). We can manage our virtual machine through the Windows Admin Center (preview) in the Azure portal. We can manage operating system functions from the Azure portal as well as work with files in the VM without using Remote Desktop or PowerShell. This feature is only available for Windows Server 2016 and Server 2019.

In this article, we are going to learn an overview of the Windows Admin Center (preview), and the functionality of the Windows Admin Center (preview).



Saturday, 22 May 2021

Azure Evening - Middle East 2021

I had successfully delivered the special session about Azure VPN and Express Route in the Azure Evening - Middle East 2021!

More than 30 participants from Qatar, Dubai, Oman, and Saudi Arabia.








Saturday, 15 May 2021

Configuring VNet Peering From Different Azure Active Directory Tenants

 In this article, we are going to learn how can we implement VNet Peering across different Azure Active Directory Tenants. VNet Peering allows you to connect two virtual networks created by using different deployment models.

 
Normally we are using a VPN gateway for connecting different subscriptions from Virtual Network to Virtual Network. At the same time, we can use VNet Peering to connect virtual networks in the same Azure subscription or different subscriptions, as long as they share the same Azure AD tenant.


Before configuring the VNet peering we need to add the Client AD Tenant user to our Azure AD, so invite them using the Azure AD.
 
Step 1
 
In the Azure Active Directory, select the Users under the management, in the Users page Click + New user, then select Invite user finally enter the user email address and click the Invite button.
Configuring VNet Peering From Different Azure Active Directory Tenants
 
Step 2
 
In the client email, we can find that the Azure AD initiation, so click Accept Invitation. 
 
Configuring VNet Peering From Different Azure Active Directory Tenants
 
Step 3
 
After accepting the Invitation, Sign out of the Azure portal and Sign in Again, we can now find the new directory added to our Azure portal.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 4
 
Repeat the same process (Step 1 to Step 3) for another Azure AD Tenant.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 5
 
Now we have to assign permission to the Invited users. In the Azure Resource Group create the Role assignment using the Access Control (IAM), select the role like Contributor or Network Contributor, and then select the user and click Save.
 
Configuring VNet Peering From Different Azure Active Directory Tenants
Step 6
 
To collect the resource ID for adding the VNet peering, to finding the Virtual Network Resource ID, go to the Virtual Network and click Properties, in the properties page you can find the Resource ID.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 7
 
Open the Virtual Network “OfficeVNet” and Select the peering under the Settings, and then click + Add.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 8
 
In the Add, peering page, enter the peering link name, and enter the Remote virtual network name.
 
After that Select, I know my resource ID, and then enter the Resource ID, after entering the Resource ID (Step 6, we have copied the resource id) you can able to find the Directory, select the Remote Azure Directory, and click Add.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 9
 
In the peering section, we can be verified that the peering status is “Initiated” because we must repeat the same settings on the Client-side.
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 10
 
Repeat the same steps (Steps 6 to Steps 8),
 
Configuring VNet Peering From Different Azure Active Directory Tenants
 
Configuring VNet Peering From Different Azure Active Directory Tenants 
 
Step 11
 
Finally, our VNet peering has been connected to both sides.
 
Configuring VNet Peering From Different Azure Active Directory Tenants
 
Configuring VNet Peering From Different Azure Active Directory Tenants

Friday, 23 April 2021

Cloud Transformation in the Government Sectors

I had a second knowledge-sharing program with the Divisional Secretaries, Director of Planning, and Accountants at the District Secretariat, Batticaloa on April 23, 2021.

We had discussed Cloud Transformations in the Government Sectors. especially how to migrate their on-premises workloads to the cloud, working with SharePoint Online and Office 365.


Click here to view the District Secretariat News


Dan TV News - https://fb.watch/57XuzWKHLz/






Friday, 16 April 2021

Global Azure 2021 - Sri Lanka

Successfully delivered the special session about  Azure VPN and ExpressRoute session at the Global Azure 2021, Organized by TechNet Leaders - Sri Lanka.

Discussed how to configure Site-to-Site VPN and ExpressRoute.


Click the below link to watch the session


https://www.youtube.com/watch?v=HpTj14gOfzs




Thursday, 15 April 2021

Global Azure 2021 - India

Successfully delivered the special session about  WordPress on Azure at the Global Azure 2021, Organized by Microsoft DEV Geeks - India.

Discussed how to install WordPress on Azure, DNS REdirection, Binding SSL Certificate.

Click the below link to watch the session

https://youtu.be/sq9Tz0nr-is?t=7818 




Friday, 9 April 2021

Cloud Transformations in the Government Sectors

 We had a special knowledge sharing program with the District Secretary (Government Agent), and other Divisional Secretaries, Director of Planning, Accountants at the District Secretariat, Batticaloa on May 9, 2021.

We had discussed Cloud Transformations in the Government Sectors. especially how to migrate their on-premises workloads to the cloud, working with SharePoint Online and Office 365.


Click here to view the District Secretariat News


Dan TV News - https://fb.watch/4UE1zUgvDs/