I would really like to be able to add DDNS Hostnames for users behind dynamic IPs which we could then add to the GCP FIrewall Rules list.

Because we are working from home more and more and there is technology such as VOIP phone handsets, IoT devices and others besides, where we don't have or can't have a VPN into say our offices and where we actually want to connect these devices anyway directly to GCP, via the GCP FIrewall using Ingress rules.

Right now GCP does not out of the box support dynamic IPs via DDNS hostnames, as you can only input the physical IP into a FIrewall Rule in the IP range; so if the IP changes which the dynamic ones do at home, well your device isn't going to be available once it does. So what I'd like to be able to do is to be able to add multiple DDNS hostnames, better still have Google provide the DDNS service that could either be configured at the user's router end or even a software service running on Macs or PC's. With that we could allow more users to work from home authenticating via GCP so that devices like VOIP phone handsets would work from the DDNS to IP address conversion in GCP Firewall.

Office.com/setup is the URL for an encounter that we've been working for a very long time. We planned it to be your work centre point insight and help you rapidly get to the applications, devices, records, and substance you use consistently. We've additionally carried knowledge into the experience that alters the experience-dependent on your exercises. Office.com incorporates the Office 365 application launcher, which opens when you click the application launcher symbol. The application launcher, which notwithstanding Office.com is likewise accessible over the suite, is a menu of your Office 365 applications and administrations that makes opening and exchanging between applications simple.
Microsoft revealed a few changes to the manner in which stuck applications chip away at Office.com and in the application launcher:
Microsoft gave administrator controls in the Azure Active Directory gateway that empower administrators with the Cloud application chairman, Application executive or Global overseer function to stick up to three applications to Office.com and the application launcher. Any application added by an administrator can be unfastened by the client whenever. Office.com and the application launcher are currently one experience and will show a similar arrangement of applications. There's no compelling reason to physically stick applications to the application launcher on the grounds that the framework currently consequently sticks applications for you dependent on utilization. Any application added consequently can be unfastened whenever. In the past experience, applications were taken out after they were unused for a specific timeframe. In the refreshed insight, applications will stay until physically unfastened. Microsoft additionally revealing a change that gives administrators through the Azure Active Directory entrance with the capacity to bunch applications and alter the perspective on the Office 365 exhibition. The Office 365 exhibition empowers you to investigate and find out about accessible applications. This customization should be possible through the "assortments" sharp edge in the Azure Active Directory administrator entry. For data on the best way to do this, see Create assortments on the My Apps entryway. Clients will see these progressions turned out soon. https://officecomsetupdownload.com/

It is useful to have stable and succinct IPv6 blocks to be used for firewalls, as well as avoiding the many other indignities of undesired NAT.

Here's how AWS does it, which is pretty good:

VPCs (=~ Network) can receive an AWS-assigned block that is internet-routable. The customer can assign subnets (=~ SubNetwork) within that space. Sidebar: a customer cannot choose the size, /64 is obliged: that's fine, it's a customary size for maximum compatibility.

Finally, network interfaces, including the default one assigned to instances upon boot, can have one or more IPv6 addresses assigned to them, or generated by AWS for your convenience.

The final result is a practically unlimited number of instances and/or IPs with public routable IPs, controlled by firewall if I do not desire inbound access, that can sit in a /64 block of my choice.

Azure does not get this right, as is often vociferously pointed out in their uservoice forum: https://feedback.azure.com/forums/217313-networking?category_id=110022. A main thing they seem to lack is IPv6 without indirections, like GCP, though they do seem to have internal routing support for it when peering VNets (=~ Network) to other networks.