Skip to content

Commit 3a9ea6a

Browse files
authored
Update README.md
1 parent e2bb7b0 commit 3a9ea6a

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,10 @@ If you would like to see a demo of the script, please check out the video below:
1414

1515
## Release notes v4.1
1616

17+
* VERSION 4.2 in BETA now, with ASA support: https://github.com/chrivand/Firepower_O365_Feed_Parser/tree/VERSION-4.2
1718
* Minor update from version v4.0 that creates 4 group objects in instead of 2.
1819
* It now creates 2 URL group objects for Optimize+Allow and for Default category, and does the same for the IP group objects.
19-
* It adds a dummy IP range (240.0.0.0/4) or dummy URL (example.com), if Microsoft does not return any addresses. Microsoft does not always return full lists. Sometimes they only return the Default URL’s for example, since they don’t own those IP ranges. This can cause a Policy Deploy failure, hence the dummy addresses.
20+
* [WARNING] It adds a dummy IP range (240.0.0.0/4) or dummy URL (example.com), if Microsoft does not return any addresses. Microsoft does not always return full lists. Sometimes they only return the Default URL’s for example, since they don’t own those IP ranges. This can cause a Policy Deploy failure, hence the dummy addresses.
2021
* Some other changes include the optimization of the script (e.g. it will only do FMC requests if a new version is detected of the O365 script).
2122
* Executing of the script is exactly the same as before, it now just creates 4 objects. The BYPASS objects are recommended to be bypassed (like in a prefilter rule), the DEFAULT objects are recommended to be treated just like other internet traffic.
2223

0 commit comments

Comments
 (0)