MS Office 365 Optimize

Console UI

1. Navigate to Manage Gateways Page
2. Click on + sign in the top right corner.
3. Click on "Create Gateway" on the Azure Cloud Gateway Card
4. Fill in the required information and click on "Create"
5. Copy the Client Registration Key
6. Click on "Deploy to Microsoft Azure". It will take you to the Azure Portal and ask you for your login credentials.
7. You will be presented with the template that needs to be filled. The first section is the Basics regarding your Subscription and Resource Group this gateway will be deployed in.
8. The second section related to resources associated with this gateway. e.g. vm name, ip address space, security groups, etc. you will paste the registration key copied in step 5. You will also need the public ssh key to use for access to this gateway remotely.
9. You will need to agree to Azure Marketplace Terms and Conditions and click to "Purchase" to continue.
10. If the NF Gateway was deployed successfully. Here is the view of the Resource Group and NF Conole UI.
11. Done

Console UI

1. Navigate to Manage Services Page under Manage Appwans
2. Click on + sign in the top right corner.
3. Click on "Create an IP Network Service"

4. Fill in the required information for the Network your wanting to access.

   Important

   Please make sure the service you want to access is behind the gateway you specify here.

5. If successfully, the service is green.

6. Done

Console UI

1. Navigate to Manage AppWANS Page under Manage Appwans
2. Click on + sign in the top right corner.
3. Click on "Component Builder Appwan"
4. Move the desired gateway (e.g. DemoGateway01) from "Available" Gateways to "Selected" Endpoints. Move the desired service (e.g. DemoServiceSsh) from "Available" to "Selected" Services.
5. Click on "Create".
6. Done

Console UI

1. Navigate to Manage Clients Page
2. Click on + sign in the top right corner.
3. Fill in the required information and click on "Create"
4. Copy the Client Registration Key
5. Install the NF Client Software by following the directions at the appropriate OS link
   1. Window
   2. Mac
6. Add this Endpoint to the AppWan
7. Once endpoint is added to the AppWan, here is what the services tab should look like.

Steps

1. Clone this repo (git clone https://github.com/netfoundry/mop.git)
2. Change directory to mop: cd mop
3. Update quickstarts/docs/api/python/etc/nf_resources.yml as so:

   environment: production
   network_action: create
   network_name: NetworkO365
   gateway_list:
   - action: create
     cloud: azure
     count: 1
     names:
     - GATEWAY-O365-01
     region: "region found by the connectivity test, e.g. eastus"
     regionalCidr:
     - 10.20.10.0/24
     regkeys: []
     resourceGroup:
       name: "you resource RG Name"
       region: "region of your RG"
     tag: null
   services:
   - action: create
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive01
     netCidr: 22
     netIp: 13.107.136.0
     type: network
   - action: create
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive02
     netCidr: 17
     netIp: 40.108.128.0
     type: network
   - action: create
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive03
     netCidr: 14
     netIp: 52.104.0.0
     type: network
   - action: create
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive04
     netCidr: 17
     netIp: 104.146.128.0
     type: network
   - action: create
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive05
     netCidr: 22
     netIp: 150.171.40.0
     type: network
   appwans:
   - action: create
     endpoints: []
     name: AppWanSharepoint
     services:
     - SharePointOneDrive01
     - SharePointOneDrive02
     - SharePointOneDrive03
     - SharePointOneDrive04
     - SharePointOneDrive05
   terraform:
     bin: terraform
     output: 'no'
     source: ./quickstarts/docs/terraform
     work_dir: .
   

4. Run this from the root folder (mop) to create network, gateway, services, and appwan throuhg NF API and deploy Virtual Machine to host NF Gateway in your Azure RG.

   python3 quickstarts/docs/api/python/source/netfoundry/nf_resources.py --file quickstarts/docs/api/python/etc/nf_resources.yml
   

5. Run this command if to keep RG (replace "RG Region" with your RG's region, e.g. centralus)

   terraform state rm module."RG Region"_rg.azurerm_resource_group.terraformgroup
   

6. Once the script is finished, all the resources in NF Console and Azure RG will have been deployed.

Example

1. Here are the parameters used in the script few needs to be changed to suit your need for eg. network_name and region_ name.

   clientId /secret: from NF console steps below.
   environment: Production
   network_name: e.g. DemoNet01
   audience: URI for the Auth0
   api_endpoint: URI for the API calls
   region_name: The region_name is the reference region or location where client will be created
               (reference closest AWS location) e.g.us-east-1
   provider: AWS
   

2. To create a unique client we can use second half of computer name below powershell cmdlet will fetch the same.

   #Set Endpoint name to second half of computer name:
   $endpoint_name = $ENV:COMPUTERNAME.Split("-")[-1]
   

3. This section creates an access token by an api call using parameters defined earlier.

   # Get a auth token from Auth0
   $auth_payload = @{
       client_id=$client_id
       client_secret=$client_secret
       audience=$audience
       grant_type='client_credentials'
   }
   $auth_json = $auth_payload | ConvertTo-Json
   
   $post_uri =  "https://netfoundry-" + $environment + ".auth0.com/oauth/token"
   
   $auth0_response = Invoke-RestMethod -Method Post -Uri $post_uri -ContentType 'application/json' -Body $auth_json
   
   $token = $auth0_response.access_token
   
   #Inserting auth token to headers for API calls
   $headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
   $headers.add("Authorization", ("Bearer " + $token))
   

4. This is how to get datacenterId and networkId which basically makes an API call to strips off unwanted information. This information will be used to create client later.

   # Get a dataCenter ID:
   
   $datacenter_uri = $api_endpoint + "/dataCenters"
   
   $dataCenter_response = Invoke-RestMethod -Method Get -Uri $datacenter_uri -ContentType 'application/json' -Headers $headers
   
   $dataCenter = $dataCenter_response._embedded.dataCenters | where { $_.locationCode -like $region_name -and $_.provider -like $provider }  | select _links
   
   $dataCenterId = ($dataCenter._links.self.href).Split("/")[-1]
   

   # Get a Network ID:
   
   $network_uri = $api_endpoint + "/networks"
   
   $network_response = Invoke-RestMethod -Method Get -Uri $network_uri -ContentType 'application/json' -Headers $headers
   
   $network = $network_response._embedded.networks | where { $_.name -like $network_name } | select _links
   
   $networkrId = ($network._links.self.href).Split("/")[-1]
   

5. Below section of the script uses computername, networkId and datacenterId from above sections to make API call create a NF client and fetch the regitration key.

   # Create an Endpoint & get reg key
   $endpoint_uri = $api_endpoint + "/networks/" + $networkrId + "/endpoints"
   $endpoint_payload  = @{
       name = $endpoint_name
       endpointType = "CL"
       dataCenterId = $dataCenterId
   }
   $endpoint_json = $endpoint_payload | ConvertTo-Json
   $endpoint_response  = Invoke-RestMethod -Method Post -Uri $endpoint_uri -ContentType 'application/json' -Body $endpoint_json -Headers $headers
   $endpoint_registration_key = $endpoint_response.registrationKey
   

6. This section will run a registration script silently to register the NF client.

   # Run registration script
   Start-Process -FilePath C:\"Program Files"\DVN\vtc_app\nfnreg $endpoint_registration_key
   

7. Once you download PS script onto your laptop and update it with your network details, run the following in the directory containing the script:

   .\NF-pwrshell.ps1
   

8. Update the following section of the resources.yaml file referenced at the beginning of the last section.

   appwans:
   - action: create
     endpoints:
     - "your endpoint name"
   

9. Run resources.py script to add the newly created endpoint to the same AppWan.

   python3 quickstarts/docs/api/python/source/netfoundry/nf_resources.py --file quickstarts/docs/api/python/etc/nf_resources.yml
   

10. Once endpoint is added to the AppWan, here is what the services tab should look like.

Verifying the performance through testing

1. Map your Business OneDrive to your local file system if not already done so.
2. Make sure the NF App is enabled.
3. Transfer large files between remote and local drive to test the performance.
4. Disable the NF App and repeat the previous step to compare the performance.
5. The performance should be at least the same if not better.

Steps

1. Change all actions to delete in quickstarts/docs/api/python/etc/nf_resources.yml as so:

   environment: production
   network_action: delete
   network_name: NetworkO365
   gateway_list:
   - action: delete
     cloud: azure
     count: 1
     names:
     - GATEWAY-O365-01
     region: eastus
     regionalCidr:
     - 10.20.10.0/24
     regkeys: []
     resourceGroup:
       name: RG_O365_Demo
       region: centralus
     tag: null
   services:
   - action: delete
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive01
     netCidr: 22
     netIp: 13.107.136.0
     type: network
   - action: delete
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive02
     netCidr: 17
     netIp: 40.108.128.0
     type: network
   - action: delete
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive03
     netCidr: 14
     netIp: 52.104.0.0
     type: network
   - action: delete
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive04
     netCidr: 17
     netIp: 104.146.128.0
     type: network
   - action: delete
     gateway: GATEWAY-O365-01
     name: SharePointOneDrive05
     netCidr: 22
     netIp: 150.171.40.0
     type: network
   appwans:
   - action: delete
     endpoints: []
     name: AppWanSharepoint
     services:
     - SharePointOneDrive01
     - SharePointOneDrive02
     - SharePointOneDrive03
     - SharePointOneDrive04
     - SharePointOneDrive05
   terraform:
     bin: terraform
     output: 'no'
     source: ./quickstarts/docs/terraform
     work_dir: .
   

2. Run this from the root folder (mop) to delete network, gateway, services, and appwan through NF API and destroy Virtual Machine hosting NF Gateway in your Azure RG.

   python3 quickstarts/docs/api/python/source/netfoundry/nf_resources.py --file quickstarts/docs/api/python/etc/nf_resources.yml